Thank you very much！
Could you please tell why the developers choose the design that token is a
cluster setting but not a column family one？
At 2011-12-18 01:44:23,"Edward Capriolo" wrote:
No. Token and partitioner are cluster wide settings. You have to run multiple
instances of Cassandra.
It has been mentioned before. In a nutshell the answer is "Do not use
ByteOrderPartitioner". It has the problem you mentioned multiple-column
families with different distributions as well as hot-spot problems.
Moving the token data to a column family level would be a large change. it
only helps th
to be blunt, this doesn't sound right to me, unless it's doing something
rather more clever to manage the memory.
i mocked up a simple class containing a byte[], ByteBuffer and long, and
the shallow size alone is 32 bytes. deep size with a byte[16], 1-byte
bytebuffer and long is 132. this is
>> I would first eliminate or confirm any GC hypothesis by running all
>> nodes with -XX:+PrintGC -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
>> -XX:+PrintGCDateStamps.
>
> Is full GC not being logged through GCInspector with the defaults ?
The GC inspect tries its best, but it's polling. Unfortuna
