it could very well be the fact that
>> gc_grace_seconds is 0 that is causing your problems. Others might have
>> other suggestions, but you could potentially use sstable2json to see the
>> raw contents of the sstable on disk and see why data is still there.
>>
>> Thanks
AM, Daniel Chia wrote:
> Is this a LCS family, or Size Tiered? Manually running compaction on LCS
> doesn't do anything until C* 2.2 (
> https://issues.apache.org/jira/browse/CASSANDRA-7272)
>
> Thanks,
> Daniel
>
> On Wed, Aug 19, 2015 at 6:56 PM, Analia Lorenzatt
> Possibly you have snapshots? If so, use nodetool to clear them.
>
> On Wed, Aug 19, 2015 at 4:54 PM, Analia Lorenzatto <
> analialorenza...@gmail.com> wrote:
>
>> Hello guys,
>>
>> I have a cassandra cluster 2.1 comprised of 4 nodes.
>>
>> I removed a
Hello guys,
I have a cassandra cluster 2.1 comprised of 4 nodes.
I removed a lot of data in a Column Family, then I ran manually a
compaction on this Column family on every node. After doing that, If I
query that data, cassandra correctly says this data is not there. But the
space on disk is e
ots?
>
> On May 15, 2015, at 2:24 PM, Analia Lorenzatto <
> analialorenza...@gmail.com> wrote:
>
> The Replication Factor = 2. The RP is the default, but not sure how to
> check it.
> I am attaching the output of: nodetool ring
>
> Thanks a lot!
>
> On Fri
The Replication Factor = 2. The RP is the default, but not sure how to
check it.
I am attaching the output of: nodetool ring
Thanks a lot!
On Fri, May 15, 2015 at 4:17 PM, Kiran mk wrote:
> run cleanup on all the nodes and wait till it completes.
> On May 15, 2015 10:47 PM, "Analia
ata distribution status across nodes ? What is the RP ?
> On May 16, 2015 12:30 AM, "Analia Lorenzatto"
> wrote:
>
>> Thanks Kiran for answering!
>>
>> I already ran cleanup on just one node. At this moment, I am running on
>> the second one, but it did n
Thanks Kiran for answering!
I already ran cleanup on just one node. At this moment, I am running on
the second one, but it did not finish there.
On Fri, May 15, 2015 at 3:37 PM, Kiran mk wrote:
> Did you try running nodetool cleanup on all the nodes ?
> On May 15, 2015 10:47 PM, &
Hello guys,
I have a cassandra cluster = 2.1.0-2 comprised of 3 nodes. I successfully
added the third node last week. After that, I ran nodetool cleanup on one
of the other two nodes, and it finished well but it increased the used disk
space.
Before running the clean up the node was 197 GB of us
Just in case I want to clarify that after bootstrapping the third node, it
got data and seemed to be working fine. But it was the last night when
the cluster started behaving in a weird way. The last node (successfully
added last week) were being reported up and down all the time. After
restarti
Hello guys,
I have a cluster 2.1.0-2 comprised of 3 nodes. The replication factor=2.
We successfully added the third node last week. After that, We ran clean
ups on one node at that time. Then we ran repairs on all the nodes, and
finally compactions on all the CFs.
Last night, I noticed the c
gards,
>
> Carlos Juzarte Rolo
> Cassandra Consultant
>
> Pythian - Love your data
>
> rolo@pythian | Twitter: cjrolo | Linkedin: *linkedin.com/in/carlosjuzarterolo
> <http://linkedin.com/in/carlosjuzarterolo>*
> Mobile: +31 6 159 61 814 | Tel: +1 613 565 8696 x1649
> www.
Hello guys,
I have a cluster comprised of 2 nodes, configured with vnodes. Using
2.1.0-2 version of cassandra.
And I am facing an issue when I want to joing a new node to the cluster.
At first starting joining but then it got stuck:
UN 1x.x.x.x 348.11 GB 256 100.0%xx
13 matches
Mail list logo
