-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[YCQL] Querying Transaction Enabled YCL table using Rust Driver v1.8 results Seg Fault: SQL Error: Execution Error. Timed out waiting for read time #1982
Comments
@davidoabile provided access to his test environment. Here's the stack trace from the core file:
|
Per @davidoabile - queries like:
runs fine on in cqlsh, but fails/crashes from their Rust program. He mentioned they are using |
Perhaps the above stack trace is unrelated to crash. When @davidoabile ran the workload again, the corresponding core file generated had this backtrace this time:
|
UPDATE: @davidoabile indicated that he was able to narrow this down further. He's running into these issues when using transaction enabled YCQL tables with Rust driver. The same table, when queried from cqlsh works just fine. |
@srhickma was able to repro this locally using Rust driver and the sample program provided by @davidoabile . Looks like the combination of using Rust driver against a transaction enabled YCQL table is somehow causing simple selects to timeout and some time segfault/crash. @srhickma - for now, assigning to you now to share the steps you used to reproduce the program. After that, we can then make a call on who can help further investigate/work on the fix. Thanks! |
This can be reproduced using the following steps:
I was able to fix this issue by manually setting the query consistency to
So this could be used as a workaround for the time being. |
This seems to be related to issue we saw with Lua Driver (#684) which was also using a default consistency level of ONE. For YB, the recommended default consistency is QUORUM (since we use Raft for distributed consensus based replication), and as @srhickma mentioned, using that workaround should unblock you. |
Thank you for the feedback and for looking I to this.
While I can work with the workaround, I personally believe the server
should detect a malformed behaviour and return an error instead of crashing
with no error message.
Regards,
David Oabile
…On Tue, 13 Aug. 2019, 06:48 Kannan Muthukkaruppan, ***@***.***> wrote:
@davidoabile <https://github.com/davidoabile> :
This seems to be related to issue we saw with Lua Driver (#684
<#684>) which was also
using a default consistency level of ONE. For YB, the recommended default
consistency is QUORUM (since we use Raft for distributed consensus based
replication), and as @srhickma <https://github.com/srhickma> mentioned,
using that workaround should unblock you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1982>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANBOC4XZYSU2SWKFYAJ3YLQEHECZANCNFSM4IJ3AB5A>
.
|
@davidoabile - you are absolutely correct. That's why we will keep this issue open, and we have re-opened #684 also. |
Jira Link: DB-2098
This is my setup
When I run SELECT * FROM articles WHERE key="key_id" LIMIT 1 using Cassandra driver this works fine.
But when I run SELECT * FROM articles LIMIT 1
get Seg fault from the server Logs can be found here 139.99.221.130:7100
Some error messages
The text was updated successfully, but these errors were encountered: