Hello Mark,
El 26/04/2010, a las 07:17, Mark Robson escribió:
> I think the solution to this would be to choose your nodes' tokens wisely
> before you start inserting data, and if possible, modify the keys to split
> them better between the nodes.
>
> For example, if your key has two parts, on
When starting your cassandra cluster, please configure the InitialToken for
each node, which make the key range balance.
On Mon, Apr 26, 2010 at 6:17 PM, Mark Robson wrote:
> On 26 April 2010 01:18, 刘兵兵 wrote:
>
>> i do some INSERT ,because i will do some scan operations, i use the
>> OrderPres
On 26 April 2010 01:18, 刘兵兵 wrote:
> i do some INSERT ,because i will do some scan operations, i use the
> OrderPreservingPartition method.
>
> the state of the cluster is showed below.
>
> as i predicated the load is very imbalance
I think the solution to this would be to choose your nodes' t
sorry, if specifying the token manually, use:
bin/nodetool -h move
2010/4/26 Roland Hänel
> 1) you can re-balance a node with
>
> bin/nodetool -h token []
>
> specify a new token manually or let the system guess one.
>
> 2) take a look into your system.log to find out why your nodes
1) you can re-balance a node with
bin/nodetool -h token []
specify a new token manually or let the system guess one.
2) take a look into your system.log to find out why your nodes are dying.
2010/4/26 刘兵兵
> i do some INSERT ,because i will do some scan operations, i use the
> OrderPres
i do some INSERT ,because i will do some scan operations, i use the
OrderPreservingPartition method.
the state of the cluster is showed below.
as i predicated the load is very imbalance, and some of the nodes down (in
some nodes,the Cassandra processes died and in others the processes are
alive
