You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 02:01:00 UTC
[jira] [Updated] (CASSANDRA-13171) Setting
-Dcassandra.join_ring=false is ambiguous
[ https://issues.apache.org/jira/browse/CASSANDRA-13171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-13171:
-----------------------------------------
Component/s: Lifecycle
Configuration
> Setting -Dcassandra.join_ring=false is ambiguous
> ------------------------------------------------
>
> Key: CASSANDRA-13171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13171
> Project: Cassandra
> Issue Type: Bug
> Components: Configuration, Lifecycle
> Reporter: Joe Olson
> Priority: Major
> Attachments: log.txt, log2.txt
>
>
> Setting -Dcassandra.join_ring=false in /etc/cassandra/jvm.options has questionable results. From the log snippet below, the value is set to false, and read. However, everything seems to happen as if it weren't....gossip occurs, and streaming data via a bulk load comes in.
> (see attached log)
> I really need this node not to join the cluster, because it is behind on its compaction, and will immediately crash (too many files open - OS ulimit is already set to 300000 temporarily). I know of no other way to do an "offline compaction"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org