[
https://issues.apache.org/jira/browse/CASSANDRA-9899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644688#comment-14644688
]
Jeremiah Jordan commented on CASSANDRA-9899:
--------------------------------------------
Should we follow the same pattern used by
minCompactionThreshold/maxCompactionThreshold for the JMX disabledWithJMX
check? If someone changes the options with alter to enable things globally,
but they had previously called disable locally through JMX, should we enable on
this node?
Thinking through this more, I think the way it works in the patch should be the
right thing. If you have enabled: false. Do nodetool enable, then nodetool
disable, then set enabled: true in the schema, as an operator I would expect it
to turn on. But bringing it up anyway just to make sure you agree :).
[~brandon.williams] WDYT?
+1 to the patch
> If compaction is disabled in schema, you can't enable a single node through
> nodetool
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-9899
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9899
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Jeremiah Jordan
> Assignee: Marcus Eriksson
> Fix For: 2.1.x
>
>
> If you disable compaction in the schema through alter table, and then try to
> enable compaction on just one node with "nodetool enableautocompaction" it
> doesn't work. WrappingCompactionStrategy needs to pass through the enable to
> the wrapped strategies.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
