[
https://issues.apache.org/jira/browse/CASSANDRA-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew F. Dennis updated CASSANDRA-2126:
-----------------------------------------
Description:
It looks like when a repair is started via nodetool and the repair takes a long
time the blocking RMI call can timeout before the repair finishes. The repair
will continue to run and correctly complete, but the caller receives a stack
trace similar to:
{noformat}
Exception in thread "main" java.rmi.UnmarshalException: Error unmarshaling
return header; nested exception is:
java.io.EOFException
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:209)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown
Source)
at
javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
at
javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
at $Proxy0.forceTableRepair(Unknown Source)
at
org.apache.cassandra.tools.NodeProbe.forceTableRepair(NodeProbe.java:155)
at org.apache.cassandra.tools.NodeCmd.optionalKSandCFs(NodeCmd.java:635)
at org.apache.cassandra.tools.NodeCmd.main(NodeCmd.java:546)
Caused by: java.io.EOFException
at java.io.DataInputStream.readByte(DataInputStream.java:250)
at
sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:195)
... 9 more
{noformat}
was:It looks like when a repair is started via nodetool and the repair takes
a long time the blocking RMI call can timeout before the repair finishes. The
repair will continue to run and correctly complete, but the caller receives a
stack trace referencing EOFException.
> RMI call times out on large repair jobs
> ---------------------------------------
>
> Key: CASSANDRA-2126
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2126
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Matthew F. Dennis
> Priority: Minor
>
> It looks like when a repair is started via nodetool and the repair takes a
> long time the blocking RMI call can timeout before the repair finishes. The
> repair will continue to run and correctly complete, but the caller receives a
> stack trace similar to:
> {noformat}
> Exception in thread "main" java.rmi.UnmarshalException: Error unmarshaling
> return header; nested exception is:
> java.io.EOFException
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:209)
> at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142)
> at com.sun.jmx.remote.internal.PRef.invoke(Unknown Source)
> at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(Unknown
> Source)
> at
> javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:993)
> at
> javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:288)
> at $Proxy0.forceTableRepair(Unknown Source)
> at
> org.apache.cassandra.tools.NodeProbe.forceTableRepair(NodeProbe.java:155)
> at
> org.apache.cassandra.tools.NodeCmd.optionalKSandCFs(NodeCmd.java:635)
> at org.apache.cassandra.tools.NodeCmd.main(NodeCmd.java:546)
> Caused by: java.io.EOFException
> at java.io.DataInputStream.readByte(DataInputStream.java:250)
> at
> sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:195)
> ... 9 more
> {noformat}
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
