[
https://issues.apache.org/jira/browse/CASSANDRA-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842844#action_12842844
]
Jonathan Ellis commented on CASSANDRA-840:
------------------------------------------
Okay. I don't know that it's worth using a re-entrant lock (since both read
locking and write are Rare Events) but that's not a big deal. I do think that
Multilock is definitely overkill.
It's safe for other threads to be messing about with existing Table references
during a mutate right? ("this doesn't help terribly much if you already have a
table reference") Because using double-checked locking in Table.open means
that most of the time that's what you're going to get.
If it's not let's see if we can come up with a way to use Concurrent operations
instead of trying to lock everyone. I think it's doable -- if we move the
modifications themselves to an executor queue, then you don't have to worry
about them stomping on each other and you only have to make sure you don't
expose changes to the rest of the systems via the CFS map until they are ready.
> Add the ability to add/remove/rename column families on a single node.
> ----------------------------------------------------------------------
>
> Key: CASSANDRA-840
> URL: https://issues.apache.org/jira/browse/CASSANDRA-840
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Gary Dusbabek
> Assignee: Gary Dusbabek
> Priority: Minor
> Fix For: 0.7
>
> Attachments: v1-0001-store-cfid-map-in-CLH.txt,
> v1-0002-establish-ordering-of-cfids.txt,
> v1-0003-add-a-cf-on-a-single-node.txt,
> v1-0004-drop-a-cf-on-a-single-node.txt,
> v1-0005-rename-a-cf-on-a-single-node.txt,
> v1-0006-alternate-locking-approach.txt
>
>
> We need the ability to manipulate the KS/CF definitions structures in
> DatabaseDescriptor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
