Dne 16.7.2013 20:45, Robert Coli napsal(a):
On Fri, Jul 12, 2013 at 2:28 AM, Radim Kolar h...@filez.com
mailto:h...@filez.com wrote:
with some very little work (less then 10 KB of code) is possible
to have online sstable splitter and exported this functionality
over JMX.
Are you
On Fri, Jul 12, 2013 at 2:28 AM, Radim Kolar h...@filez.com wrote:
with some very little work (less then 10 KB of code) is possible to have
online sstable splitter and exported this functionality over JMX.
Are you volunteering? If so, I'd totally dig using the patch! :D
=Rob
with some very little work (less then 10 KB of code) is possible to have
online sstable splitter and exported this functionality over JMX.
On Thu, Jul 11, 2013 at 9:43 PM, Takenori Sato ts...@cloudian.com wrote:
I made the repository public. Now you can checkout from here.
https://github.com/cloudian/support-tools
checksstablegarbage is the tool.
Enjoy, and any feedback is welcome.
Thanks very much, useful tool!
Out of
It's light. Without -v option, you can even run it against just a SSTable
file without needing the whole Cassandra installation.
- Takenori
On Sat, Jul 13, 2013 at 6:18 AM, Robert Coli rc...@eventbrite.com wrote:
On Thu, Jul 11, 2013 at 9:43 PM, Takenori Sato ts...@cloudian.com wrote:
I
Hi
About a year ago, we did a major compaction in our cassandra cluster (a
n00b mistake, I know), and since then we've had huge sstables that never
get compacted, and we were condemned to repeat the major compaction process
every once in a while (we are using SizeTieredCompaction strategy, and
Thanks Takenori,
Looks like the tool provides some good info that people can use. It would
be great if you can share it with the community.
On Thu, Jul 11, 2013 at 6:51 AM, Takenori Sato ts...@cloudian.com wrote:
Hi,
I think it is a common headache for users running a large Cassandra
Perhaps I should already know this but why is running a major compaction
considered so bad? We're running 1.1.6.
Thanks.
On Thu, Jul 11, 2013 at 7:51 AM, Takenori Sato ts...@cloudian.com wrote:
Hi,
I think it is a common headache for users running a large Cassandra
cluster in production.
Information is only deleted from Cassandra during a compaction. Using
SizeTieredCompaction, compaction only occurs when a number of similarly sized
sstables are combined into a new sstable.
When you perform a major compaction, all sstables are combined into one, very
large, sstable. As a
On Thu, Jul 11, 2013 at 2:46 AM, Tomàs Núnez tomas.nu...@groupalia.comwrote:
Hi
About a year ago, we did a major compaction in our cassandra cluster (a
n00b mistake, I know), and since then we've had huge sstables that never
get compacted, and we were condemned to repeat the major compaction
Hi,
I made the repository public. Now you can checkout from here.
https://github.com/cloudian/support-tools
checksstablegarbage is the tool.
Enjoy, and any feedback is welcome.
Thanks,
- Takenori
On Thu, Jul 11, 2013 at 10:12 PM, srmore comom...@gmail.com wrote:
Thanks Takenori,
Looks
11 matches
Mail list logo
