datastax
Recurring error
SYSTEM:
MAC
INSTALLED:
using docker compose as mentioned in github
ISSUE DESCRIPTION & REPLICATION
after the instances comes up, and I leave the notebook for some time I keep on getting the error as mentioned below:
{"detailedMessage": "Query parsing failed at line 1, error message: token recognition error at: 'y'", "requestId": "< a long token>", "code":"MalformedQueryException"
The query is absolutely fine and runs before.
OVERCOMING THIS ISSUE
I cannot overcome this issue just by running docker-compose down and docker-compose up --build
I have to run docker-compose down, and docker system prune, and then docker-compose up --build for things to start running.
HYPOTHESIS
can this be happening if I have two tabs open with two different notebooks? Users sometimes do want to keep two notebooks open just for comparison, or copying and pasting purposes.
Regards, Gourav Sengupta
Hi Gourav. A couple questions. How long are you leaving the instance up before you see this issue? Also, are you "sleeping" your machine or anything during that time? Also, if you look at the logs of the docker container created for the server do you see any errors popping up? Finally, how much memory do you have allocated to Docker?
"can this be happening if I have two tabs open with two different notebooks" I do this all of the time with no issues. Not saying it's definitely not the issue, but nothing I've ever seen.
Hi David, Thanks a ton for coming back. the system may have gone to sleep but I do not recollect that to have happened before. I did try to see the errors in the docker logs, but there was nothing that appeared different over there. I am trying to use Python to connect with the cassandra cluster in order to generate graph dashboard using dash and cytoscape as well, and am ensuring that the database and session are shutdown. Let me work on this a bit and try to see if there is a method to reproduce this error, in case I am not able to I will close this issue. I am trying to introduce take quite a few members in our team through the notes therefore I will come back to you in case this issue reoccurs in some other system. Regards, Gourav Sengupta
Hi David, Thanks a ton for coming back. the system may have gone to sleep but I do not recollect that to have happened before. I did try to see the errors in the docker logs, but there was nothing that appeared different over there. I am trying to use Python to connect with the cassandra cluster in order to generate graph dashboard using dash and cytoscape as well, and am ensuring that the database and session are shutdown. Let me work on this a bit and try to see if there is a method to reproduce this error, in case I am not able to I will close this issue. I am trying to introduce take quite a few members in our team through the notes therefore I will come back to you in case this issue reoccurs in some other system. Regards, Gourav Sengupta
Hi David, Thanks a ton for coming back. the system may have gone to sleep but I do not recollect that to have happened before. I did try to see the errors in the docker logs, but there was nothing that appeared different over there. I am trying to use Python to connect with the cassandra cluster in order to generate graph dashboard using dash and cytoscape as well, and am ensuring that the database and session are shutdown. Let me work on this a bit and try to see if there is a method to reproduce this error, in case I am not able to I will close this issue. I am trying to introduce take quite a few members in our team through the notes therefore I will come back to you in case this issue reoccurs in some other system. Regards, Gourav Sengupta
Ok great, that sounds good. I'm also reaching out to our internal teams to see if this is something anyone has seen before.