[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499999#comment-13499999 ]
Aleksey Yeschenko commented on CASSANDRA-4753: ---------------------------------------------- That particular error has been fixed some time ago (same issue that was causing batchlog timeouts in beta1). So there is really no need to special-case timeout-reporter for local node - such cases just should not happen. However, I added a check for local node to StorageProxy.shouldHint so that no issue like this one pops in the future. > Timeout reporter writes hints for the local node > ------------------------------------------------ > > Key: CASSANDRA-4753 > URL: https://issues.apache.org/jira/browse/CASSANDRA-4753 > Project: Cassandra > Issue Type: Bug > Affects Versions: 1.2.0 beta 1 > Reporter: Aleksey Yeschenko > Assignee: Aleksey Yeschenko > Fix For: 1.2.0 > > Attachments: 4753.txt > > > MessagingService.java:330 calls StorageProxy.scheduleLocalHint() without > checking if the local node is the target. This causes > StorageProxy.scheduleLocalHint to throw AssertionError sometimes. > Got this error when some batches are timed out. This can happen because even > local batches now go through StorageProxy.sendMessages and aren't just > rm.apply()'d. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira