Here is the line in the source code for 1.1.0:

And it's refactored later to this, and the message was removed.


From: "Dean Hiller" <>
To:, "Wei Zhu" <>
Sent: Monday, June 24, 2013 12:04:10 PM
Subject: Re: AssertionError: Unknown keyspace?

Yes, it would be nice at startup just to say don't list your seed node as this node and then fail out and we would have known this a long long time ago ;).

From: Wei Zhu <<>>
Reply-To: "<>" <<>>, Wei Zhu <<>>
Date: Monday, June 24, 2013 12:36 PM
To: "<>" <<>>
Subject: Re: AssertionError: Unknown keyspace?

I have got bitten by it once. At least there should be a message saying, there is no streaming data since it's a seed node.
I searched the source code, the message was there and it got removed at certain version.


From: Robert Coli <<>>
Sent: Monday, June 24, 2013 10:34 AM
Subject: Re: AssertionError: Unknown keyspace?

On Mon, Jun 24, 2013 at 6:04 AM, Hiller, Dean <<>> wrote:
> Oh shoot, this is a seed node.  Is there documentation on how to bootstrap
> a seed node?  If I have seeds of A, B, C for every machine on the ring and
> I am bootstrapping node B, do I just modify cassandra.yaml and remove node
> B from the yaml file temporarily and boot it up

Yes. The only thing that makes a node fail that check is being in its
own seed list. But if the node is in other nodes' seed lists, those
nodes will contact it anyway. This strongly implies that the
"contains()" check there is the wrong test, but I've never nailed that
down and/or filed a ticket on it. Conversation at the summit suggests
I should, making a note to do so...