cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3522) Fatal exception in thread Thread
Date Tue, 22 Nov 2011 16:06:40 GMT

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

Jonathan Ellis commented on CASSANDRA-3522:
-------------------------------------------

please upgrade to 1.0.3 to verify that this isn't an already-fixed bug like CASSANDRA-2961
                
> Fatal exception in thread Thread 
> ---------------------------------
>
>                 Key: CASSANDRA-3522
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3522
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0
>         Environment: Ubuntu 10.04 LTS - 8GB mem/ 360 GB disk - Hosted by RS
>            Reporter: Gabriel Rosendorf
>            Priority: Minor
>
> Seeing this recurring exception on all machines in a 5 node cluster.  Recently upgraded
to 1.0.0 from 0.7.2. 
> ERROR [MutationStage:20] 2011-11-22 15:25:55,758 AbstractCassandraDaemon.java (line 133)
Fatal exception in thread Thread[MutationStage:20,5,main]
> java.lang.AssertionError
> 	at org.apache.cassandra.locator.TokenMetadata.getToken(TokenMetadata.java:273)
> 	at org.apache.cassandra.service.StorageProxy$4.run(StorageProxy.java:350)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> 	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 	at java.lang.Thread.run(Thread.java:662)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message