cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9034) AssertionError in SizeEstimatesRecorder
Date Fri, 27 Mar 2015 07:14:53 GMT

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

Aleksey Yeschenko commented on CASSANDRA-9034:
----------------------------------------------

bq. Aleksey Yeschenko if you are happy could you take care of committing please?

Doubt I'll ever be happy, so let's not wait for that. Committed to both 2.1 and 3.0, as {{bd48424}},
thanks.

> AssertionError in SizeEstimatesRecorder
> ---------------------------------------
>
>                 Key: CASSANDRA-9034
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9034
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Trunk (52ddfe412a)
>            Reporter: Stefania
>            Assignee: Carl Yeksigian
>            Priority: Minor
>             Fix For: 3.0
>
>         Attachments: 9034-trunk.txt
>
>
> One of the dtests of CASSANDRA-8236 (https://github.com/stef1927/cassandra-dtest/tree/8236)
raises the following exception unless I set {{-Dcassandra.size_recorder_interval=0}}:
> {code}
> ERROR [OptionalTasks:1] 2015-03-25 12:58:47,015 CassandraDaemon.java:179 - Exception
in thread Thread[OptionalTasks:1,5,main]
> java.lang.AssertionError: null
>         at org.apache.cassandra.service.StorageService.getLocalTokens(StorageService.java:2235)
~[main/:na]
>         at org.apache.cassandra.db.SizeEstimatesRecorder.run(SizeEstimatesRecorder.java:61)
~[main/:na]
>         at org.apache.cassandra.concurrent.DebuggableScheduledThreadPoolExecutor$UncomplainingRunnable.run(DebuggableScheduledThreadPoolExecutor.java:82)
~[main/:na]
>         at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_76]
>         at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [na:1.7.0_76]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
[na:1.7.0_76]
>         at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[na:1.7.0_76]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[na:1.7.0_76]
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.7.0_76]
>         at java.lang.Thread.run(Thread.java:745) [na:1.7.0_76]
> INFO  [RMI TCP Connection(2)-127.0.0.1] 2015-03-25 12:59:23,189 StorageService.java:863
- Joining ring by operator request
> {code}
> The test is {{start_node_without_join_test}} in _pushed_notifications_test.py_ but starting
a node that won't join the ring might be sufficient to reproduce the exception (I haven't
tried though).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message