[
https://issues.apache.org/jira/browse/CASSANDRA-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778067#comment-13778067
]
Brandon Williams commented on CASSANDRA-6084:
---------------------------------------------
It's not the amount of connections so much as how fast they're trying to spawn
and connect. The "couldn't get the split because something happened at the
network level" is about the best message you can get there on the client side.
If you pushed logging up in o.a.c.thrift on the server you might get something
useful, but that's kind of impractical.
> java.io.IOException: Could not get input splits
> -----------------------------------------------
>
> Key: CASSANDRA-6084
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6084
> Project: Cassandra
> Issue Type: Bug
> Components: Hadoop
> Environment: Osx 10.8.5
> Java 1.7
> Cassandra 1.2.10
> Pig 0.9.2/0.11.1
> Reporter: Cyril Scetbon
> Assignee: Alex Liu
> Attachments: 6084_debug.txt
>
>
> see http://www.mail-archive.com/[email protected]/msg32414.html
> I've noticed that if I restart Cassandra I get more errors for the first
> minutes, although it's accessible through cqlsh without issue.
> I have tested on a 1-node (Osx Laptop) and 4-nodes (Ubuntu servers) and got
> the same error. I tried with version 1.2.6, 1.2.8, 1.2.9, 1.2.10 without
> success
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
