-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with importing table to DQOps #29
Comments
The first problem that the container failed to start was caused by starting the container both with -d (background, daemon mode) and -it (interactive mode). The second issue with the error is probably also caused by the same problem that two instances of DQOps are running and one instance was stopping. You can also check out the most recent version of DQOps (1.4.0), which was released yesterday. The bug in the file TableStatusCacheImpl.java (line 99) is fixed there, and the code is protected from issues caused by too early access to the cache before it was fully initialized. If you are still stuck on this issue, please use the Calendly link on our website (https://dqops.com/contact-us/) and find a timeslot on the calendar. We can review the issue, because I am also curious what was special on your environment that you faced these problems. |
Pulled the latest image and deploy once again, the error above is gone, but replaced with another one
Im deploying with this docker-compose
Any idea? thanks in advance |
It is a race condition during the initialization, probably the rest api is called when the backend is starting and has not yet initialized all caches. It is fixed in the develop branch. |
Description:
Error with importing table to DQOps, happened with Trino and MySQL.
Deployment:
Docker
docker run -v [enter the path to your local userhome folder]:/dqo/userhome -d -it -m=4g -p 8888:8888 dqops/dqo run
Not having
-it
leads into instant collapsed docker container even though first deployment worked fine.What happened:
First, i deployed DQOps without the
-it
flag. It worked like a charm, everything is fine until i restarted my device, and then restarted DQOps container, it ran for about 7 to 10 seconds and collapsed. If-it
, it worked again.But here comes the second issue i faced. When i created data sources (Trino and MySQL in this case), it connected as expected, the schemas and tables were showing, but when i import those table, it stuck loading and a new notification poped up:
How to reproduce:
As described above, it all started after a docker restart and i deleted the folder used as dqhome in my device for a fresh start.
What to expect:
Everything works just fine again, including the Incident is not being created when there's checking issue (i wonder if it depends on the severity of the issue or not)
Any help would be much appreciated!
Thanks in advance.
The text was updated successfully, but these errors were encountered: