[ 
https://issues.apache.org/jira/browse/CASSANDRA-6084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777777#comment-13777777
 ] 

Alex Liu commented on CASSANDRA-6084:
-------------------------------------

The following is the error from pig log

{code}
Caused by: java.util.concurrent.ExecutionException: java.io.IOException: failed 
connecting to all endpoints 127.0.0.1, connections: rpc_endpoint: 127.0.0.1, 
listen_endpoint: 127.0.0.1, host: 127.0.0.1, port: 9160
, errors: java.io.IOException: Unable to connect to server 127.0.0.1:9160
        at 
org.apache.cassandra.hadoop.ConfigHelper.createConnection(ConfigHelper.java:575)
        at 
org.apache.cassandra.hadoop.AbstractColumnFamilyInputFormat.getSubSplits(AbstractColumnFamilyInputFormat.java:278)
        at 
org.apache.cassandra.hadoop.AbstractColumnFamilyInputFormat.access$200(AbstractColumnFamilyInputFormat.java:64)
        at 
org.apache.cassandra.hadoop.AbstractColumnFamilyInputFormat$SplitCallable.call(AbstractColumnFamilyInputFormat.java:224)
        at 
org.apache.cassandra.hadoop.AbstractColumnFamilyInputFormat$SplitCallable.call(AbstractColumnFamilyInputFormat.java:209)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:722)
Caused by: org.apache.thrift.transport.TTransportException: 
java.net.SocketException: Connection reset by peer
        at org.apache.thrift.transport.TSocket.open(TSocket.java:183)
        at 
org.apache.thrift.transport.TFramedTransport.open(TFramedTransport.java:81)
        at 
org.apache.cassandra.thrift.TFramedTransportFactory.openTransport(TFramedTransportFactory.java:42)
        at 
org.apache.cassandra.hadoop.ConfigHelper.createConnection(ConfigHelper.java:570)
        ... 9 more
Caused by: java.net.SocketException: Connection reset by peer
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
        at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
        at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391)
        at java.net.Socket.connect(Socket.java:579)
        at org.apache.thrift.transport.TSocket.open(TSocket.java:178)
        ... 12 more
 
        at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252)
        at java.util.concurrent.FutureTask.get(FutureTask.java:111)
        at 
org.apache.cassandra.hadoop.AbstractColumnFamilyInputFormat.getSplits(AbstractColumnFamilyInputFormat.java:187)
        ... 21 more
{code}

There is no error in Cassandra system log.

It can't connection to 127.0.0.1:9160 sometimes when vnode is enable where 
there are more connection requests. Can it be something related to rpc_* 
settings in cassandra.yaml?
{code
rpc_server_type: sync
# rpc_min_threads: 16
# rpc_max_threads: 2048
# rpc_send_buff_size_in_bytes:
# rpc_recv_buff_size_in_bytes:
rpc_keepalive: true
{code}

Note: the issue is gone when vnode is disable where there is much less rpc 
connections

 
                
> 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/user@cassandra.apache.org/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

Reply via email to