Adeel,

It may be a problem in the remote node, could you check the system.log?

Also you might want to check the rpc_timeout_in_ms in both nodes, maybe an increase in this parameter helps.





On Fri, Apr 12, 2013 at 9:17 AM, <adeel.akbar@panasiangroup.com> wrote:
Hi,

I have started repair on newly added node with -pr and this nodes exist on another data center. I have 5MB internet connection and configured setstreamthroughput 1. After some time repair goes hang and following meesage found in logs;

# /opt/apache-cassandra-1.1.4/bin/nodetool -h localhost ring
Address         DC          Rack        Status State   Load            Effective-Ownership Token
                                                                                           169417178424467235000914166253263322299
10.0.0.3        DC1         RAC1        Up     Normal  93.26 GB        66.67%              0
10.0.0.4        DC1         RAC1        Up     Normal  89.1 GB         66.67%              56713727820156410577229101238628035242
10.0.0.15       DC1         RAC1        Up     Normal  72.87 GB        66.67%              113427455640312821154458202477256070484
10.40.1.103     DC2         RAC1        Up     Normal  48.59 GB        100.00%             169417178424467235000914166253263322299


 INFO [HintedHandoff:1] 2013-04-12 17:05:49,411 HintedHandOffManager.java (line 372) Timed out replaying hints to /10.40.1.103; aborting further deliveries
 INFO [HintedHandoff:1] 2013-04-12 17:05:49,411 HintedHandOffManager.java (line 390) Finished hinted handoff of 0 rows to endpoint /10.40.1.103

Why we getting this message and how I prevent repair from this error.

Regards,

Adeel Akbar