"ERROR 08:53:47,678 Internal error processing batch_mutate
java.lang.IllegalStateException: replication factor (3) exceeds number
of endpoints (1)"
You already answered 
"It always keeps showing only one node and mentions that it is handling 100% of the load." 

Cluster think only one node is present in ring, it doesn't agree RF=3  it is expecting RF=1.

Original Q: I m not exactly sure what is the problem. But

Does nodetool ring show all the host?
What is your seed list? 
Is bootstrapped node has seed ip of its own?

AFAIK gossip work even without actively joining a ring.
On Tue, Aug 2, 2011 at 7:21 AM, Aishwarya Venkataraman
<cyberaishu@gmail.com> wrote:
> Replies inline.
> Thanks,
> Aishwarya
> On Tue, Aug 2, 2011 at 7:12 AM, Sorin Julean <sorin.julean@gmail.com> wrote:
>> Hi,
>>  Until someone answers  with more details, few questions:
>>  1. did you moved the system keyspace as well ?
> Yes. But I deleted the LocationInfo* files under the system folder.
> Shall I go ahead and delete the entire system folder ?
>>  2. the gossip IP of the new nodes are the same as the old ones ?
> No. The Ip is different.
>>  3. which cassandra version are you running ?
> I am using 0.8.1
>> If 1. is yes and 2. is no, for a quick fix: take down the cluster, remove
>> system keyspace, bring the cluster up and bootstrap the nodes.
>> Kind regards,
>> Sorin
>> On Tue, Aug 2, 2011 at 2:53 PM, Aishwarya Venkataraman
>> <cyberaishu@gmail.com> wrote:
>>> Hello,
>>> I recently migrated 400 GB of data that was on a different cassandra
>>> cluster (3 node with RF= 3) to a new cluster. I have a 3 node  cluster
>>> with replication factor set to three. When I run nodetool ring, it
>>> does not show me all the nodes in the cluster. It always keeps showing
>>> only one node and mentions that it is handling 100% of the load. But
>>> when I look at the logs, the nodes are able to talk to each other via
>>> the gossip protocol. Why does this happen ? Can you tell me what I am
>>> doing wrong ?
>>> Thanks,
>>> Aishwarya