[
https://issues.apache.org/jira/browse/CASSANDRA-15200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Jirsa updated CASSANDRA-15200:
-----------------------------------
Resolution: Not A Problem
Status: Resolved (was: Triage Needed)
JIRA is for bug reports and feature discussion, not questions and answers.
> Can a new adding node store other keyspaces' data and add permission of
> one more machine failure for a replicator 2's keyspace in the new even number
> nodes' DC?
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-15200
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15200
> Project: Cassandra
> Issue Type: Improvement
> Reporter: gloCalHelp.com
> Priority: Normal
>
> Question on adding a new node, replicator and how many machine failes?
> Can a new adding node store other keyspaces' data and add permission of
> one more machine failure for a replicator 2's keyspace in the new even number
> nodes' DC?
> Cassandra's designing of adding a new node for only a keyspace is
> quite good for a high load keyspace and token allocation. But I have
> aquestions:
> 1st, if the high load keyspace has a replicator of only 2, and
> original cluster has only 3 datanodes, if adding a new node to form a 4
> datanodes for this keyspace, then there will permit how many machine failes
> for this 2 replicator keyspace's 4 data nodes center?
> 2nd, on cassandra's official web, there is a line of : To use this
> approach, the new node must be started with the JVM option
> -Dcassandra.allocate_tokens_for_keyspace=<keyspace>, where <keyspace> is the
> keyspace from which the algorithm can find the load information to optimize
> token assignment for.
> Does this mean that a new adding node can only store a keyspace's data?
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
