Re: Fwd: Re: Problem on setup Cassandra v4.0.1 cluster

[onmstester onmstester via user <us...@cassandra.apache.org>]

I encountered the same problem again with same error logs(this time with Apache Cassandra 4.0.6 and a new cluster), but unlike the previous time, hostname config was fine. After days of try and fail, finally i've found the root cause: time in faulty server has a 2 minute difference and not in sync with other servers in the cluster!, just synced the time and problem fixed.

I wonder if community could provide more information at log level for such problems (to prevent users struggle and debug these sort of stuff), because these two problems (faulty hostname config and non-sync server timestamp) are common due to manual config or no one thought such problems could prevent a Cassandra node from joining the cluster!


Sent using https://www.zoho.com/mail/








---- On Mon, 31 Jan 2022 16:35:50 +0330 onmstester onmstester <on...@zoho.com> wrote ---





Once again it was related to hostname configuration (I remember had problem with this multiple times before even on different applications), this time the root cause was a typo in one of multiple config files for hostname (different name on /etc/hostname with /etc/hosts)! I fixed that and now there is no problem.



I wonder how Cassandra-3.11 worked?!



P.S: Default dc name in version 4 was changed to datacenter1 (from dc1) and it seems to cause a bit of problem with previous configs(default one in rack-dc conf still is dc1).



Thank you



Best Regards

Sent using https://www.zoho.com/mail/






============ Forwarded message ============
From: Erick Ramirez <ma...@datastax.com>
To: <ma...@cassandra.apache.org>
Date: Mon, 31 Jan 2022 15:06:21 +0330
Subject: Re: Problem on setup Cassandra v4.0.1 cluster
============ Forwarded message ============












TP stats indicate pending gossip. Check that the times are synchronised on both nodes (use NTP) since it can prevent gossip from working.



I'd also suggest looking at the logs on both nodes to see what other WARN and ERROR messages are being reported. Cheers!