You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2012/10/03 17:48:08 UTC
[jira] [Created] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Aleksey Yeschenko created CASSANDRA-4753:
--------------------------------------------
Summary: 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: Jonathan Ellis
Fix For: 1.2.0 beta 2
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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500301#comment-13500301 ]
Jonathan Ellis commented on CASSANDRA-4753:
-------------------------------------------
Hmm. We actually have a couple problems here.
# We do allow local writes to be dropped, but
# Nobody writes hints for dropped local writes
# If local hints were attempted, they would error out (what v2 was trying to fix)
We actually do want to hint batchlog inserts to maintain the contract of "timed out means it's in progress, you do not have to retry."
I'm not sure what the best way to add hinting (actually, retry-on-hint-stage) code for insertLocal is though. One option would be to just make local writes non-droppable, but then we lose our backpressure mechanism of a full hint stage causing OverloadedException, and a poorly behaving client could OOM the coordinator with a lot of local writes.
> 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, 4753-v2.txt, 4753-v3.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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500146#comment-13500146 ]
Aleksey Yeschenko commented on CASSANDRA-4753:
----------------------------------------------
Something like v3.
> 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, 4753-v2.txt, 4753-v3.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
[jira] [Updated] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4753:
--------------------------------------
Reviewer: jbellis
Assignee: Aleksey Yeschenko (was: Jonathan Ellis)
> 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
>
>
> 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
[jira] [Updated] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4753:
--------------------------------------
Priority: Minor (was: Major)
> 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: Jonathan Ellis
> Priority: Minor
> Fix For: 1.2.1
>
> Attachments: 4753.txt, 4753-v2.txt, 4753-v3.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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468628#comment-13468628 ]
Aleksey Yeschenko commented on CASSANDRA-4753:
----------------------------------------------
See https://issues.apache.org/jira/browse/CASSANDRA-4542?focusedCommentId=13451479&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13451479
and https://issues.apache.org/jira/browse/CASSANDRA-4542?focusedCommentId=13451486&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13451486
> 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: Jonathan Ellis
> Fix For: 1.2.0 beta 2
>
>
> 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
[jira] [Updated] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4753:
--------------------------------------
Attachment: 4753-v2.txt
It's valid for local writes to timeout, but we don't want to just drop them on the floor if they do. v2 attached.
> 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, 4753-v2.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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501479#comment-13501479 ]
Jonathan Ellis commented on CASSANDRA-4753:
-------------------------------------------
Here is one solution.
- Created LocalMutationRunnable that retries with hint backpressure if it gets dropped
- Added an updated v3, with an additional assert to make sure we don't introduce a bug if we decide to allow using the coordinator as a batchlog member in non-single-node clusters
> 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, 4753-v2.txt, 4753-v3.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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468632#comment-13468632 ]
Jonathan Ellis commented on CASSANDRA-4753:
-------------------------------------------
Sounds like the right solution is to add a local-only apply the way we do for normal Mutations.
> 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: Jonathan Ellis
> Fix For: 1.2.0 beta 2
>
>
> 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
[jira] [Updated] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4753:
--------------------------------------
Comment: was deleted
(was: Here is one solution.
- Created LocalMutationRunnable that retries with hint backpressure if it gets dropped
- Added an updated v3, with an additional assert to make sure we don't introduce a bug if we decide to allow using the coordinator as a batchlog member in non-single-node clusters)
> 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, 4753-v2.txt, 4753-v3.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
[jira] [Updated] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-4753:
--------------------------------------
Reviewer: iamaleksey (was: jbellis)
Fix Version/s: (was: 1.2.0)
1.2.1
Assignee: Jonathan Ellis (was: Aleksey Yeschenko)
> 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: Jonathan Ellis
> Fix For: 1.2.1
>
> Attachments: 4753.txt, 4753-v2.txt, 4753-v3.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
[jira] [Updated] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-4753:
-----------------------------------------
Attachment: 4753-v3.txt
> 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, 4753-v2.txt, 4753-v3.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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468631#comment-13468631 ]
Aleksey Yeschenko commented on CASSANDRA-4753:
----------------------------------------------
Special-casing for local inserts might be worth it now that abm is the default and we went even futher with CASSANDRA-4738.
> 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: Jonathan Ellis
> Fix For: 1.2.0 beta 2
>
>
> 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
[jira] [Updated] (CASSANDRA-4753) Timeout reporter writes hints for
the local node
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-4753:
-----------------------------------------
Attachment: 4753.txt
> 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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Jonathan Ellis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13501483#comment-13501483 ]
Jonathan Ellis commented on CASSANDRA-4753:
-------------------------------------------
Here is one solution: http://github.com/jbellis/cassandra/branches/4753-5
- Created LocalMutationRunnable that retries with hint backpressure if it gets dropped
- Added an updated v3, with an additional assert to make sure we don't introduce a bug if we decide to allow using the coordinator as a batchlog member in non-single-node clusters
> 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, 4753-v2.txt, 4753-v3.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
[jira] [Commented] (CASSANDRA-4753) Timeout reporter writes hints
for the local node
Posted by "Aleksey Yeschenko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500136#comment-13500136 ]
Aleksey Yeschenko commented on CASSANDRA-4753:
----------------------------------------------
You are right. There is still the option of special-casing local endpoint for syncWriteToBatchlog and asyncRemoveFromBatchlog. I know single-node clusters are not a pirority, but still. That would also make this issue go away.
> 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, 4753-v2.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