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

Brandon Williams commented on CASSANDRA-18935:
----------------------------------------------

bq. why not set the flag when doing nodetool enablebinary if we found the flag 
is not true

Yes, that's the correct fix, having enablebinary also call setRpcReady(true).  
Given that the call appears idempotent, we could move it into the start/stop 
native transport calls directly.  It's probably a vestige of having thrift and 
the native protocol.

> Unable to write to counter table if native transport is disabled on startup
> ---------------------------------------------------------------------------
>
>                 Key: CASSANDRA-18935
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18935
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Core, Legacy/CQL
>            Reporter: Cameron Zemek
>            Assignee: Stefan Miklosovic
>            Priority: Normal
>             Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.x
>
>         Attachments: 18935-3.11.patch
>
>
>  
> {code:java}
>         if ((nativeFlag != null && Boolean.parseBoolean(nativeFlag)) || 
> (nativeFlag == null && DatabaseDescriptor.startNativeTransport()))
>         {
>             startNativeTransport();
>             StorageService.instance.setRpcReady(true);
>         } {code}
> The startup code here only sets RpcReady if native transport is enabled. If 
> you call 
> {code:java}
> nodetool enablebinary{code}
> then this flag doesn't get set.
> But with the change from CASSANDRA-13043 it requires RpcReady set to true in 
> order to get a leader for the counter update.
> Not sure what the correct fix is here, seems to only really use this flag for 
> counters. So thinking perhaps the fix is to just move this outside the if 
> condition.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to