On Thu, Aug 30, 2012 at 10:39 PM, Casey Deccio wrote:
>> In what way are the lookups "failing"? Is there an exception?
>>
> No exception--just failing in that the data should be there, but isn't.
At ConsistencyLevel.ONE or QUORUM?
If you are bootstrapping the node, I would expect there to be no
On Thu, Aug 30, 2012 at 11:21 AM, Rob Coli wrote:
> On Thu, Aug 30, 2012 at 10:18 AM, Casey Deccio wrote:
> > I'm adding a new node to an existing cluster that uses
> > ByteOrderedPartitioner. The documentation says that if I don't
> configure a
> > token, then one will be automatically generat
On Thu, Aug 30, 2012 at 10:18 AM, Casey Deccio wrote:
> I'm adding a new node to an existing cluster that uses
> ByteOrderedPartitioner. The documentation says that if I don't configure a
> token, then one will be automatically generated to take load from an
> existing node.
> What I'm finding is
All,
I'm adding a new node to an existing cluster that uses
ByteOrderedPartitioner. The documentation says that if I don't configure a
token, then one will be automatically generated to take load from an
existing node. What I'm finding is that when I add a new node, (super)
column lookups begin
