[
https://issues.apache.org/jira/browse/CASSANDRA-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12869652#action_12869652
]
Frank Du commented on CASSANDRA-1073:
-------------------------------------
I figured out what specific condition will cause the exception:
1. The steps will cause the issue.
I have latest source code setup in eclipse. I use cassandra-cli tool, insert
some data, and terminate cli by clicking Terminate icon in eclipse console. It
means that the method CliMain.disconnect() is not invoked. Terminate cassandra,
and start it up again. Now the exception occurs every time I invoke
get_range_slices() API.
2. The steps won't cause the issue.
I inserted some data by typing {{set}} commands. Then I quit cassandra-cli by
typing {{exit}}. It means that the method CliMain.disconnect() is invoked.
Restart cassandra, and everything works greatly!
So, I guess that the server side code (corresponding to TTransport.close
method) may not handle well situations when a client drops unexpectedly.
Please let me know if any supplemental information is required to fix the
issue.
- Frank
> EOFException with Cassandra.Client.get_range_slices() API
> ---------------------------------------------------------
>
> Key: CASSANDRA-1073
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1073
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.6
> Reporter: Frank Du
> Fix For: 0.6.2
>
>
> Below is the snippet I tried to run. The keyspace is named 'Keyspac1', with
> only 1 column family named 'CF1'.
> ColumnParent cp = new ColumnParent("CF1");
>
> SlicePredicate predicate = new SlicePredicate();
> SliceRange sliceRange = new SliceRange();
> sliceRange.setStart(new byte[0]);
> sliceRange.setFinish(new byte[0]);
> predicate.setSlice_range(sliceRange);
>
> KeyRange range = new KeyRange(10);
> range.setStart_key("".getBytes());
> range.setEnd_key("".getBytes());
>
> client.set_keyspace(keyspace);
> List<KeySlice> slices = client.get_range_slices(cp, predicate,
> range, ConsistencyLevel.ONE);
> Then an EOFException was spit out. For readability, it is included in the
> next comment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
