cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10898) Migrate Compaction Strategy Node by Node
Date Mon, 04 Jan 2016 10:19:39 GMT


Sylvain Lebresne commented on CASSANDRA-10898:

bq.  it looks like in your example and would be the IP addresses of which
Cassandra Nodes have been overridden to use a different compaction strategy?


bq. And honestly for how little you would need this a quick dirty script might be fine.

Just to clarify, my suggestion is not meant to be _only_ for the use case you opened the ticket
for. I just think it could be a neat option to be able to test specific settings on a single
(or a couple of) node easily for settings that are intrinsically local (so at least compaction
strategy, caching options and sstable compression for now). And while those changes can be
done through JMX through scripts, it's slightly involved and not having it persist across
can be operationally annoying. But this is nothing more than a nice to have in my mind.

bq. Another option I thought of is having a mechanism to control the maximum simultaneous
compactions for table in the cluster.

Sure, though that solve a slightly different problem than the one I made my suggestion for
(as explained above). But being able to somewhat limit the amount of concurrent compaction
going on in the cluster is also an interesting suggestion, and not just for when changing
compaction strategy in fact. It's probably a bit more involved however.

> Migrate Compaction Strategy Node by Node
> ----------------------------------------
>                 Key: CASSANDRA-10898
>                 URL:
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Compaction, Tools
>            Reporter: Andrew From
> It would be a great feature to be able to slowly change the compaction strategy of a
ColumnFamily node-by-node instead of cluster wide. Currently if you change it cluster wide
there's no good way to predict how long it will take. Thus the process could run for days
while you still need the live data, but the cluster responds much more slowly due to the compaction
strategy migration.
> I stumbled across
which gave me the idea. I was thinking this would be a nice feature to add to NodeTool, provided
that the strategy in the blog is sound I wouldn't mind going ahead with the dev work to automate
it. If not I would love to hear other ideas on how to best make this happen.

This message was sent by Atlassian JIRA

View raw message