a node is full CPU (all other
cores are idleing), so I assume I'm CPU bound on node side. But why ? What the
node is doing ? Why does it take so long time ?
--
Mike Neir
Liquid Web, Inc.
Infrastructure Administrator
cause this fix in 1.0.11:
* fix 1.0.x node join to mixed version cluster, other nodes >= 1.1
(CASSANDRA-4195)
-Jeremiah
--
Mike Neir
Liquid Web, Inc.
Infrastructure Administrator
Is there anything that you can link that describes the pitfalls you mention? I'd
like a bit more information. Just for clarity's sake, are you recommending 1.0.9
-> 1.0.12 -> 1.1.12 -> 1.2.x? Or would 1.0.9 -> 1.1.12 -> 1.2.x suffice?
Regarding the placement strategy mentioned in a different p
.
MN
On 08/30/2013 12:15 PM, Robert Coli wrote:
On Fri, Aug 30, 2013 at 8:57 AM, Mike Neir mailto:m...@liquidweb.com>> wrote:
I'm faced with the need to update a 36 node cluster with roughly 25T of data
on disk to a version of cassandra in the 1.2.x series. While it seem
are no schema changes going on, the node should be able to just hop back into
the cluster without error and without transitioning through the "Joining" state.
--
Mike Neir
Liquid Web, Inc.
Infrastructure Administrator
