As I see the state 162.243.109.94 is UL(Up/Leaving) so maybe this is causing
the problem.
On Sunday, October 26, 2014 11:57 PM, Tim Dunphy
wrote:
Hey all,
I'm trying to decommission a node.
First I'm getting a status:
[root@beta-new:/usr/local] #nodetool statusNote: Ownership inf
contention
for the same partition key - (this might not cause OOM but will certainly
massively tax GC and it sounds like you don’t have a lot/any headroom).
On Aug 12, 2014, at 12:31 PM, Robert Coli wrote:
>
>On Tue, Aug 12, 2014 at 9:34 AM, jivko donev wrote:
>
>We have a node wi
wrote:
On Tue, Aug 12, 2014 at 9:34 AM, jivko donev wrote:
We have a node with commit log director ~4G. During start-up of the node on
commit log replaying the used heap space is constantly growing ending with OOM
error.
>
>
>
>The heap size and new heap size properties are -
appreciated. If you need more information fell free to
ask.
Thanks,
Jivko Donev
Hi,
Our environment will consist of cluster with size not bigger than 2 to 4 nodes
per cluster(all located in the same DC). We want to ensure that every node in
the cluster will own 100% of the data. A node adding(or removing) procedure
will be automated so we want to ensure we're making the ri