incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gurpreet Singh <>
Subject Re: disk full error while bootstrapping
Date Fri, 10 Sep 2010 04:38:04 GMT
I did set autobootstrap true. It got the new token, and even proceeded to
print the message that its bootstrapping, however the source node just didnt
show any activity. At a later point, when i tried again (after the other
bootstrap from the other source was finished), it did proceed, however that
failed with a different exception during streaming. Anyway, getting rid of
that node now, as it has less memory (4  gigs) and giving streaming
exceptions, so just scping data out right now.


On Thu, Sep 9, 2010 at 9:09 PM, Jonathan Ellis <> wrote:

> On Thu, Sep 9, 2010 at 2:24 PM, Gurpreet Singh <>
> wrote:
> > D was once a part of the cluster, but had gone down because of disk
> issues.
> > Its back up, it still has the old data, however to bootstrap again, i
> > deleted the old Location db (is that a good practise?), and so i see it
> did
> > take a new token, but is not proceeding with the bootstrap.
> sounds like you didn't set autobootstrap=true.
> > Also, a question about the storage config file. When I brought up B, the
> > seeds configured in B's config was just A. When I am bringing up C and D,
> > the seeds configured in their config file are both A and B. B's config
> still
> > says the seed is A. For B to be a seed, does its own config need to also
> say
> > that its a seed.
> no.  but best practice is for all nodes to have the same seeds list to
> avoid confusion.
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of Riptano, the source for professional Cassandra support

View raw message