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 the BOP/OOP, which along with supercolumns are highly NOT suggested in all cases, but people still seem to gravitate to them. 2011/12/18 魏金仙 <sei_...@126.com> > 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" <edlinuxg...@gmail.com> wrote: > > No. Token and partitioner are cluster wide settings. You have to run > multiple instances of Cassandra. > > 2011/12/17 魏金仙 <sei_...@126.com> > >> My question is whether two groups of "initial_token" can coexist since >> our goal is to partition data of each column family uniformly on 5 nodes. >> >> I deployed Cassandra 0.7.4 on a cluster of 5 nodes, using >> orderPreservingPartitioner. Two column families named CF1 and CF2 are >> created on one keyspace. Keys of CF1 go as a0,a1,a2,a3... while those of >> CF2 are b0,b1,b2.... >> Assume that the initial_tokens should be set as a0,a2,a4,a6,a8 if you >> want to achieve load balance of CF1 and as b0,b2,b4,b6,b8 for CF2. >> Is it possible two set "initial_token" as: initial_token: a0,b0? >> >> Thank you! >> >> >> > > >
