[jira] [Commented] (CASSANDRA-20785) Journal.TopologyUpdate should not store the local topology as it can be inferred from the global on

["David Capwell (Jira)" <ji...@apache.org>]

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

David Capwell commented on CASSANDRA-20785:
-------------------------------------------

Starting commit

CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-20785-trunk-14E9F023-8ACB-4A6F-BB95-1269757DAD08]|[build|unknown]|[build|unknown]|


> Journal.TopologyUpdate should not store the local topology as it can be inferred from the global on
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-20785
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20785
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Accord
>            Reporter: David Capwell
>            Assignee: David Capwell
>            Priority: Normal
>             Fix For: 6.x
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> Journal.TopologyUpdate stores the global and local topology details, but local is just global.forNode(myId).  By removing local we are able to shrink the cost of topology update events in the journal



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

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