[CASSANDRA-11217] Only log yaml config once, at startup

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 2.2.6, 3.0.5, 3.5
• Component/s: Legacy/Core, Local/Config
• Severity: Low
• Assignee: Jason Brown
• Reporter: Jason Brown

Authors

Jason Brown

Reviewers

Paulo Motta

• Created: 23/Feb/16 14:53
• Updated: 16/Apr/19 09:30
• Resolved: 02/Mar/16 21:05

Description

CASSANDRA-6456 introduced a feature where the yaml is dumped in the log. At startup this is a nice feature, but I see that it’s actually triggered every time it handshakes with a node and fails to connect and the node happens to be a seed (see here). Calling DD.getseeds() calls the SeedProvider, and if you happen to use SimpleSeedProvider it will reload the yaml config, and once again dump it out to the log.

It's debatable if DD.getseeds() should trigger a reload (which I added in CASSANDRA-5459) or whether reloading the seeds should be a different method (it probably should), but we shouldn't keep logging the yaml config on every connection failure to a seed.