[
https://issues.apache.org/jira/browse/CASSANDRA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-358:
-------------------------------------
Attachment: 358-v11.patch
The thing is, we _want_ all copies of SMD to be updated when we change the
token or Bad Things Could Happen. The only way to do that sanely is to make
SMD a singleton.
Here is v11, which you can think of as either v10 with SMD a singleton, or v8
with the call to setStorageId moved into updateToken and synchronized. :)
> SystemTable.initMetadata throws an NPE when called twice
> --------------------------------------------------------
>
> Key: CASSANDRA-358
> URL: https://issues.apache.org/jira/browse/CASSANDRA-358
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jeff Hodges
> Attachments: 358-5.patch, 358-7.patch, 358-v10.patch, 358-v11.patch,
> 358-v8.patch, 358-v9.patch
>
>
> While this is not the expected use case of it, SystemTable.initMetadata
> throws an NPE when called twice in the same process. The error points to
> tokenColumn being null even through cf is not at line 111.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
