Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <9369981.354571285190552757.JavaMail.jira@thor>
Date: Wed, 22 Sep 2010 17:22:32 -0400 (EDT)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1534) errors reading while
 bootstrapping
In-Reply-To: <15607864.353581285189053241.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913802#action_12913802 ] 

Jonathan Ellis commented on CASSANDRA-1534:
-------------------------------------------

does bs against a vanilla no-decom cluster work?

> errors reading while bootstrapping
> ----------------------------------
>
>                 Key: CASSANDRA-1534
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1534
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Brandon Williams
>             Fix For: 0.7 beta 2
>
>
> I loaded a 4 node cluster with 1M rows from stress.py, decommissioned a node, and then began bootstrapping it while performing constant reads against the others with stress.py.  After sleeping for 90s, the bootstrapping node started throwing many errors like this:
> ERROR 16:51:48,667 Fatal exception in thread Thread[READ_STAGE:1270,5,main]
> java.lang.RuntimeException: Cannot service reads while bootstrapping!
>         at org.apache.cassandra.db.ReadVerbHandler.doVerb(ReadVerbHandler.java:67)
>         at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:50)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>         at java.lang.Thread.run(Thread.java:636)
> And I began receiving timeout errors with stress.py.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.