Please find attached netstat -t -as output for the node on which repair hung
and the node which never got Merkle Tree Request.
ThanksAnuj
On Sunday, 29 November 2015 11:13 PM, Anuj Wadehra
wrote:
Hi All,
I am summarizing the setup, problem & key observations till now:
Setup: Cassan
Hi All,
I am summarizing the setup, problem & key observations till now:
Setup: Cassandra 2.0.14. 2 DCs with 3 nodes each connected via 10Gbps VPN. We
run repair with -par and -pr option.
Problem: Repair Hangs. Merkle Tree Responses are not received from one or more
nodes in remote DC.
Observa
Yes. I think you are correct, problem might have resolved via Cassandra restart
rather than increasing request timeout.
We are NOT on EC2. We have 2 interfaces on each node: one private and one
public.
We have strange configuration and we need to correct it as per the
recommendation at
https:/