cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13171) Setting -Dcassandra.join_ring=false is ambiguous
Date Mon, 06 Feb 2017 08:36:41 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853690#comment-15853690
] 

Stefan Podkowinski commented on CASSANDRA-13171:
------------------------------------------------

Did you use {{-Dcassandra.start_gossip=false}}? I'm missing a "Not starting gossip as requested."
message from your logs.

> Setting -Dcassandra.join_ring=false is ambiguous
> ------------------------------------------------
>
>                 Key: CASSANDRA-13171
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13171
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Joe Olson
>         Attachments: log2.txt, log.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
(v6.3.15#6346)

Mime
View raw message