Re: data not replicated on new node

[Vladimir Yudovin]

try SELECT for some undoubtedly old data with consistency ALL

It's worth to turn trace on for this query.



Best regards, Vladimir Yudovin, 

Winguzone - Hosted Cloud Cassandra
Launch your cluster in minutes.





 On Mon, 21 Nov 2016 02:05:35 -0500Vladimir Yudovin 
vla...@winguzone.com wrote 




can the node "talk" with the others? (i.e. telnet to the other nodes on 
port 7000). 

According to nodetool status all nodes are joined and UP, so they seems to be 
able talk one with other (though there still can be connectivity issues). Are 
all nodes on internal network (e.g. 10.x.x.x) in the same locations?



I suspect that ... the old data stored on the first 2 nodes are not 
replicated on the new node.

Can you try SELECT for some undoubtedly old data with consistency ALL (just one 
raw is enough)?



Also the whole event sequence are not clear: you had two nodes with data, then 
added third. When did you change replication factor for existing keyspace? Or 
it was created with factor three?



Best regards, Vladimir Yudovin, 

Winguzone - Hosted Cloud Cassandra
Launch your cluster in minutes.





 On Mon, 21 Nov 2016 01:28:54 -0500Shalom Sagges 
shal...@liveperson.com wrote 




I believe the logs should show you what the issue is. 

Also, can the node "talk" with the others? (i.e. telnet to the other nodes on 
port 7000). 







 
Shalom Sagges
 
DBA
 
T: +972-74-700-4035
 

 
 
 
 We Create Meaningful Connections
 
 

 









On Sun, Nov 20, 2016 at 8:50 PM, Bertrand Brelier 
bertrand.brel...@gmail.com wrote:









This message may contain confidential and/or privileged information. 

If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this message 
or any information herein. 

If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.


Hello Jonathan,



No, the new node is not a seed in my cluster. 



When I ran nodetool bootstrap resume

Node is already bootstrapped.



Cheers,



Bertrand




On Sun, Nov 20, 2016 at 1:43 PM, Jonathan Haddad j...@jonhaddad.com 
wrote:

Did you add the new node as a seed? If you did, it wouldn't bootstrap, and you 
should run repair. 

On Sun, Nov 20, 2016 at 10:36 AM Bertrand Brelier 
bertrand.brel...@gmail.com wrote:

Hello everybody,



I am using a 3-node Cassandra cluster with Cassandra 3.0.10.



I recently added a new node (to make it a 3-node cluster).



I am using a replication factor of 3 , so I expected to have a copy of

the same data on each node :



CREATE KEYSPACE mydata WITH replication = {'class': 'SimpleStrategy',

'replication_factor': '3'}  AND durable_writes = true;



But the new node has  less data that the other 2 :



Datacenter: datacenter1

===

Status=Up/Down

|/ State=Normal/Leaving/Joining/Moving

--  Address   Load   Tokens   Owns (effective)  Host

ID   Rack

UN  XXX.XXX.XXX.XXX  53.28 GB   256  100.0% xx  rack1

UN  XXX.XXX.XXX.XXX  64.7 GB256  100.0% xx  rack1

UN  XXX.XXX.XXX.XXX  1.28 GB256  100.0% xx  rack1





On the new node :



/XX/data-6d674a40efab11e5b67e6d75503d5d02/:

total 1.2G



on one of the old nodes :



/XX/data-6d674a40efab11e5b67e6d75503d5d02/:

total 52G





I am monitoring the amount of data on each node, and they grow at the

same rate. So I suspect that my new data are replicated on the 3 nodes

but the old data stored on the first 2 nodes are not replicated on the

new node.



I ran nodetool repair (on each node, one at a time), but the new node

still does not have a copy of the old data.



Could you please help me understand why the old data is not replicated

to the new node ? Please let me know if you need further information.



Thank you,



Cheers,



Bertrand

Re: data not replicated on new node

[Vladimir Yudovin]

can the node "talk" with the others? (i.e. telnet to the other nodes on 
port 7000). 

According to nodetool status all nodes are joined and UP, so they seems to be 
able talk one with other (though there still can be connectivity issues). Are 
all nodes on internal network (e.g. 10.x.x.x) in the same locations?



I suspect that ... the old data stored on the first 2 nodes are not 
replicated on the new node.

Can you try SELECT for some undoubtedly old data with consistency ALL (just one 
raw is enough)?



Also the whole event sequence are not clear: you had two nodes with data, then 
added third. When did you change replication factor for existing keyspace? Or 
it was created with factor three?



Best regards, Vladimir Yudovin, 

Winguzone - Hosted Cloud Cassandra
Launch your cluster in minutes.





 On Mon, 21 Nov 2016 01:28:54 -0500Shalom Sagges 
shal...@liveperson.com wrote 




I believe the logs should show you what the issue is. 

Also, can the node "talk" with the others? (i.e. telnet to the other nodes on 
port 7000). 




 


 
Shalom Sagges
 
DBA
 
T: +972-74-700-4035
 

 
 
 
 We Create Meaningful Connections
 
 

 

 







On Sun, Nov 20, 2016 at 8:50 PM, Bertrand Brelier 
bertrand.brel...@gmail.com wrote:









This message may contain confidential and/or privileged information. 

If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this message 
or any information herein. 

If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.


Hello Jonathan,



No, the new node is not a seed in my cluster. 



When I ran nodetool bootstrap resume

Node is already bootstrapped.



Cheers,



Bertrand




On Sun, Nov 20, 2016 at 1:43 PM, Jonathan Haddad j...@jonhaddad.com 
wrote:

Did you add the new node as a seed? If you did, it wouldn't bootstrap, and you 
should run repair. 

On Sun, Nov 20, 2016 at 10:36 AM Bertrand Brelier 
bertrand.brel...@gmail.com wrote:

Hello everybody,

 

 I am using a 3-node Cassandra cluster with Cassandra 3.0.10.

 

 I recently added a new node (to make it a 3-node cluster).

 

 I am using a replication factor of 3 , so I expected to have a copy of

 the same data on each node :

 

 CREATE KEYSPACE mydata WITH replication = {'class': 'SimpleStrategy',

 'replication_factor': '3'}  AND durable_writes = true;

 

 But the new node has  less data that the other 2 :

 

 Datacenter: datacenter1

 ===

 Status=Up/Down

 |/ State=Normal/Leaving/Joining/Moving

 --  Address   Load   Tokens   Owns (effective)  Host

 ID   Rack

 UN  XXX.XXX.XXX.XXX  53.28 GB   256  100.0% xx  rack1

 UN  XXX.XXX.XXX.XXX  64.7 GB256  100.0% xx  rack1

 UN  XXX.XXX.XXX.XXX  1.28 GB256  100.0% xx  rack1

 

 

 On the new node :

 

 /XX/data-6d674a40efab11e5b67e6d75503d5d02/:

 total 1.2G

 

 on one of the old nodes :

 

 /XX/data-6d674a40efab11e5b67e6d75503d5d02/:

 total 52G

 

 

 I am monitoring the amount of data on each node, and they grow at the

 same rate. So I suspect that my new data are replicated on the 3 nodes

 but the old data stored on the first 2 nodes are not replicated on the

 new node.

 

 I ran nodetool repair (on each node, one at a time), but the new node

 still does not have a copy of the old data.

 

 Could you please help me understand why the old data is not replicated

 to the new node ? Please let me know if you need further information.

 

 Thank you,

 

 Cheers,

 

 Bertrand

 

Re: data not replicated on new node

[Shalom Sagges]

I believe the logs should show you what the issue is.
Also, can the node "talk" with the others? (i.e. telnet to the other nodes
on port 7000).


Shalom Sagges
DBA
T: +972-74-700-4035
 
 We Create Meaningful Connections



On Sun, Nov 20, 2016 at 8:50 PM, Bertrand Brelier <
bertrand.brel...@gmail.com> wrote:

> Hello Jonathan,
>
> No, the new node is not a seed in my cluster.
>
> When I ran nodetool bootstrap resume
> Node is already bootstrapped.
>
> Cheers,
>
> Bertrand
>
> On Sun, Nov 20, 2016 at 1:43 PM, Jonathan Haddad 
> wrote:
>
>> Did you add the new node as a seed? If you did, it wouldn't bootstrap,
>> and you should run repair.
>> On Sun, Nov 20, 2016 at 10:36 AM Bertrand Brelier <
>> bertrand.brel...@gmail.com> wrote:
>>
>>> Hello everybody,
>>>
>>> I am using a 3-node Cassandra cluster with Cassandra 3.0.10.
>>>
>>> I recently added a new node (to make it a 3-node cluster).
>>>
>>> I am using a replication factor of 3 , so I expected to have a copy of
>>> the same data on each node :
>>>
>>> CREATE KEYSPACE mydata WITH replication = {'class': 'SimpleStrategy',
>>> 'replication_factor': '3'}  AND durable_writes = true;
>>>
>>> But the new node has  less data that the other 2 :
>>>
>>> Datacenter: datacenter1
>>> ===
>>> Status=Up/Down
>>> |/ State=Normal/Leaving/Joining/Moving
>>> --  Address   Load   Tokens   Owns (effective)  Host
>>> ID   Rack
>>> UN  XXX.XXX.XXX.XXX  53.28 GB   256  100.0% xx  rack1
>>> UN  XXX.XXX.XXX.XXX  64.7 GB256  100.0% xx  rack1
>>> UN  XXX.XXX.XXX.XXX  1.28 GB256  100.0% xx  rack1
>>>
>>>
>>> On the new node :
>>>
>>> /XX/data-6d674a40efab11e5b67e6d75503d5d02/:
>>> total 1.2G
>>>
>>> on one of the old nodes :
>>>
>>> /XX/data-6d674a40efab11e5b67e6d75503d5d02/:
>>> total 52G
>>>
>>>
>>> I am monitoring the amount of data on each node, and they grow at the
>>> same rate. So I suspect that my new data are replicated on the 3 nodes
>>> but the old data stored on the first 2 nodes are not replicated on the
>>> new node.
>>>
>>> I ran nodetool repair (on each node, one at a time), but the new node
>>> still does not have a copy of the old data.
>>>
>>> Could you please help me understand why the old data is not replicated
>>> to the new node ? Please let me know if you need further information.
>>>
>>> Thank you,
>>>
>>> Cheers,
>>>
>>> Bertrand
>>>
>>>
>

-- 
This message may contain confidential and/or privileged information. 
If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this 
message or any information herein. 
If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.

RE: lots of DigestMismatchException in cassandra3

[Adeline.Pan]

Hi Tommy,
Thank you for the reply, but I don't think this is the reason, because we don't 
have any static column.

--
Regards, Adeline



From: Tommy Stendahl [mailto:tommy.stend...@ericsson.com]
Sent: Thursday, November 17, 2016 5:16 PM
To: user@cassandra.apache.org
Subject: Re: lots of DigestMismatchException in cassandra3


Hi,

Could it be 
CASSANDRA-12090?

Regards,
/Tommy
On 2016-11-17 09:47, 
adeline@thomsonreuters.com wrote:
Hi,

We are using Cassandra 3.7 and we have a single datacenter of 4 nodes, RF =3, 
and the consistency level is quorum.
I found lots of DigestMismatchException in debug.log, as below:
DEBUG [ReadRepairStage:11] 2016-11-17 08:24:57,066 ReadCallback.java:235 - 
Digest mismatch:
org.apache.cassandra.service.DigestMismatchException: Mismatch for key 
DecoratedKey(-7187709033646443438, 
000801586f9538000405f72c7a04000300) 
(c8d67cfae7be8470ca1786eaa0d8968e vs 3aa974d3eca302682c6f31ca250ea641)
at 
org.apache.cassandra.service.DigestResolver.resolve(DigestResolver.java:85) 
~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.service.ReadCallback$AsyncRepairRunner.run(ReadCallback.java:226)
 ~[apache-cassandra-3.7.jar:3.7]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_25]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_25]
INFO  [HintsDispatcher:5] 2016-11-17 08:25:06,958 HintsStore.java:126 - Deleted 
hint file bcd84017-6068-4a76-be89-96c0130599f3-1479371095876-1.hints
INFO  [HintsDispatcher:5] 2016-11-17 08:25:06,962 
HintsDispatchExecutor.java:263 - Finished hinted handoff of file 
bcd84017-6068-4a76-be89-96c0130599f3-1479371095876-1.hints to endpoint 
bcd84017-6068-4a76-be89-96c0130599f3
DEBUG [GossipStage:1] 2016-11-17 08:25:32,551 FailureDetector.java:456 - 
Ignoring interval time of 2003165297 for /10.52.153.107
DEBUG [CompactionExecutor:9] 2016-11-17 08:25:33,034 CompactionTask.java:223 - 
Compacted (3b3d7600-ac9f-11e6-8b55-03fd515998e4) 4 sstables to 
[/data/c878jrn/data/pc_object_data_beta/vsc_data-53935ff0a74811e69ab46393a19c464a/mb-2256-big,]
 to level=0.  85.011MiB to 53.580MiB (~63% of original) in 75,524ms.  
Throughput = 726.471KiB/s.  0 total partitions merged to 15,552.  Partition 
merge counts were {1:11623, 2:3543, 3:385, 4:1, }
ERROR [MessagingService-Incoming-/10.52.153.109] 2016-11-17 08:25:42,126 
CassandraDaemon.java:217 - Exception in thread 
Thread[MessagingService-Incoming-/10.52.153.109,5,main]
java.io.IOError: java.io.IOException: Corrupt empty row found in unfiltered 
partition
at 
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer$1.computeNext(UnfilteredRowIteratorSerializer.java:224)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.db.rows.UnfilteredRowIteratorSerializer$1.computeNext(UnfilteredRowIteratorSerializer.java:212)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.utils.AbstractIterator.hasNext(AbstractIterator.java:47) 
~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize30(PartitionUpdate.java:681)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.db.partitions.PartitionUpdate$PartitionUpdateSerializer.deserialize(PartitionUpdate.java:642)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:331)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:350)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.db.Mutation$MutationSerializer.deserialize(Mutation.java:287)
 ~[apache-cassandra-3.7.jar:3.7]
at org.apache.cassandra.net.MessageIn.read(MessageIn.java:114) 
~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.net.IncomingTcpConnection.receiveMessage(IncomingTcpConnection.java:190)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.net.IncomingTcpConnection.receiveMessages(IncomingTcpConnection.java:178)
 ~[apache-cassandra-3.7.jar:3.7]
at 
org.apache.cassandra.net.IncomingTcpConnection.run(IncomingTcpConnection.java:92)
 ~[apache-cassandra-3.7.jar:3.7]
Caused by: java.io.IOException: Corrupt empty row found in unfiltered partition
at 

Re: Is Centos 7 Supported for Version 3.0

[Shalom Sagges]

Thanks Vladimir!


Shalom Sagges
DBA
T: +972-74-700-4035
 
 We Create Meaningful Connections



On Sun, Nov 20, 2016 at 10:24 PM, Vladimir Yudovin 
wrote:

> Hi,
>
> Centos 7 has Java 8 available, so there shouldn't be any problem to run
> Casandra.
>
> Best regards, Vladimir Yudovin,
>
> *Winguzone  - Hosted Cloud
> CassandraLaunch your cluster in minutes.*
>
>
>  On Sun, 20 Nov 2016 11:14:07 -0500*Shalom Sagges
> >* wrote 
>
> Hi Guys,
>
> A simple question for which I couldn't find an answer in the docs.
> Is Centos 7 supported on DataStax Community Edition v3.0.9?
>
> Thanks!
>
>
>
> Shalom Sagges
> DBA
> T: +972-74-700-4035
> 
> 
> 
> We Create Meaningful Connections
>
> 
>
>
>
> This message may contain confidential and/or privileged information.
> If you are not the addressee or authorized to receive this on behalf of
> the addressee you must not use, copy, disclose or take action based on this
> message or any information herein.
> If you have received this message in error, please advise the sender
> immediately by reply email and delete this message. Thank you.
>
>
>

-- 
This message may contain confidential and/or privileged information. 
If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this 
message or any information herein. 
If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.

Re: Node replacement failed in 2.2

[Paulo Motta]

Is there any chance the replaced node recently resumed bootstrap, joined
with join_ring=false or write_survey=true? If so, perhaps this could be
related to CASSANDRA-12935.

Otherwise gossip tokens being empty is definitely unexpected behavior and
you should probably file another ticket with more details/context (such as
gossip debug logs of replacement and other nodes, and if the replacement
node had the same or different ip as the original node since they are
slightly different code paths after #8523).

2016-11-18 19:07 GMT-02:00 Dikang Gu :

> Paulo, the tokens field for 2401:db00:2130:4091:face:0:13:0 shows
> "TOKENS: not present", on all live nodes. It means tokens are missing,
> right? What would cause this?
>
> Thanks.
> Dikang.
>
> On Fri, Nov 18, 2016 at 11:15 AM, Paulo Motta 
> wrote:
>
>> What does nodetool gossipinfo shows for endpoint /2401:db00:2130:4091:
>> face:0:13:0 ? Does it contain the TOKENS attribute? If it's missing, is
>> it only missing on this node or other nodes as well?
>>
>> 2016-11-18 17:02 GMT-02:00 Dikang Gu :
>>
>>> Hi, I encountered couple times that I could not replace a down node due
>>> to error:
>>>
>>> 2016-11-17_19:33:58.70075 Exception (java.lang.RuntimeException)
>>> encountered during startup: Could not find tokens for
>>> /2401:db00:2130:4091:face:0:13:0 to replace
>>> 2016-11-17_19:33:58.70489 ERROR 19:33:58 [main]: Exception encountered
>>> during startup
>>> 2016-11-17_19:33:58.70491 java.lang.RuntimeException: Could not find
>>> tokens for /2401:db00:2130:4091:face:0:13:0 to replace
>>> 2016-11-17_19:33:58.70491   at org.apache.cassandra.service.S
>>> torageService.prepareReplacementInfo(StorageService.java:525)
>>> ~[apache-cassandra-2.2.5+git20160315.c29948b.jar:2.2.5+git20
>>> 160315.c29948b]
>>> 2016-11-17_19:33:58.70492   at org.apache.cassandra.service.S
>>> torageService.prepareToJoin(StorageService.java:760)
>>> ~[apache-cassandra-2.2.5+git20160315.c29948b.jar:2.2.5+git20
>>> 160315.c29948b]
>>> 2016-11-17_19:33:58.70492   at org.apache.cassandra.service.S
>>> torageService.initServer(StorageService.java:693)
>>> ~[apache-cassandra-2.2.5+git20160315.c29948b.jar:2.2.5+git20
>>> 160315.c29948b]
>>> 2016-11-17_19:33:58.70492   at org.apache.cassandra.service.S
>>> torageService.initServer(StorageService.java:585)
>>> ~[apache-cassandra-2.2.5+git20160315.c29948b.jar:2.2.5+git20
>>> 160315.c29948b]
>>> 2016-11-17_19:33:58.70492   at org.apache.cassandra.service.C
>>> assandraDaemon.setup(CassandraDaemon.java:300)
>>> [apache-cassandra-2.2.5+git20160315.c29948b.jar:2.2.5+git201
>>> 60315.c29948b]
>>> 2016-11-17_19:33:58.70493   at org.apache.cassandra.service.C
>>> assandraDaemon.activate(CassandraDaemon.java:516)
>>> [apache-cassandra-2.2.5+git20160315.c29948b.jar:2.2.5+git201
>>> 60315.c29948b]
>>> 2016-11-17_19:33:58.70493   at org.apache.cassandra.service.C
>>> assandraDaemon.main(CassandraDaemon.java:625)
>>> [apache-cassandra-2.2.5+git20160315.c29948b.jar:2.2.5+git201
>>> 60315.c29948b]
>>> 2016-11-17_19:33:58.70649 INFO  19:33:58 [StorageServiceShutdownHook]:
>>> Announcing shutdown
>>> 2016-11-17_19:34:00.70967 INFO  19:34:00 [StorageServiceShutdownHook]:
>>> Waiting for messaging service to quiesce
>>> 2016-11-17_19:34:00.71066 INFO  19:34:00 
>>> [ACCEPT-/2401:db00:2130:4091:face:0:13:0]:
>>> MessagingService has terminated the accept() thread
>>>
>>> Did not find a relevant ticket for this, is anyone aware of this?
>>>
>>> Thanks!
>>>
>>> --
>>> Dikang
>>>
>>>
>>
>
>
> --
> Dikang
>
>

Re: Is Centos 7 Supported for Version 3.0

[Vladimir Yudovin]

Hi,



Centos 7 has Java 8 available, so there shouldn't be any problem to run 
Casandra.



Best regards, Vladimir Yudovin, 

Winguzone - Hosted Cloud Cassandra
Launch your cluster in minutes.





 On Sun, 20 Nov 2016 11:14:07 -0500Shalom Sagges 
shal...@liveperson.com wrote 




Hi Guys, 



A simple question for which I couldn't find an answer in the docs. 

Is Centos 7 supported on DataStax Community Edition v3.0.9?



Thanks!



 


 
Shalom Sagges
 
DBA
 
T: +972-74-700-4035
 

 
 
 
 We Create Meaningful Connections
 
 

 

 









This message may contain confidential and/or privileged information. 

If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this message 
or any information herein. 

If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.

Unsubscribe

[Brian Fleming]

Re: data not replicated on new node

[Bertrand Brelier]

Hello Jonathan,

No, the new node is not a seed in my cluster.

When I ran nodetool bootstrap resume
Node is already bootstrapped.

Cheers,

Bertrand

On Sun, Nov 20, 2016 at 1:43 PM, Jonathan Haddad  wrote:

> Did you add the new node as a seed? If you did, it wouldn't bootstrap, and
> you should run repair.
> On Sun, Nov 20, 2016 at 10:36 AM Bertrand Brelier <
> bertrand.brel...@gmail.com> wrote:
>
>> Hello everybody,
>>
>> I am using a 3-node Cassandra cluster with Cassandra 3.0.10.
>>
>> I recently added a new node (to make it a 3-node cluster).
>>
>> I am using a replication factor of 3 , so I expected to have a copy of
>> the same data on each node :
>>
>> CREATE KEYSPACE mydata WITH replication = {'class': 'SimpleStrategy',
>> 'replication_factor': '3'}  AND durable_writes = true;
>>
>> But the new node has  less data that the other 2 :
>>
>> Datacenter: datacenter1
>> ===
>> Status=Up/Down
>> |/ State=Normal/Leaving/Joining/Moving
>> --  Address   Load   Tokens   Owns (effective)  Host
>> ID   Rack
>> UN  XXX.XXX.XXX.XXX  53.28 GB   256  100.0% xx  rack1
>> UN  XXX.XXX.XXX.XXX  64.7 GB256  100.0% xx  rack1
>> UN  XXX.XXX.XXX.XXX  1.28 GB256  100.0% xx  rack1
>>
>>
>> On the new node :
>>
>> /XX/data-6d674a40efab11e5b67e6d75503d5d02/:
>> total 1.2G
>>
>> on one of the old nodes :
>>
>> /XX/data-6d674a40efab11e5b67e6d75503d5d02/:
>> total 52G
>>
>>
>> I am monitoring the amount of data on each node, and they grow at the
>> same rate. So I suspect that my new data are replicated on the 3 nodes
>> but the old data stored on the first 2 nodes are not replicated on the
>> new node.
>>
>> I ran nodetool repair (on each node, one at a time), but the new node
>> still does not have a copy of the old data.
>>
>> Could you please help me understand why the old data is not replicated
>> to the new node ? Please let me know if you need further information.
>>
>> Thank you,
>>
>> Cheers,
>>
>> Bertrand
>>
>>

Re: data not replicated on new node

[Jonathan Haddad]

Did you add the new node as a seed? If you did, it wouldn't bootstrap, and
you should run repair.
On Sun, Nov 20, 2016 at 10:36 AM Bertrand Brelier <
bertrand.brel...@gmail.com> wrote:

> Hello everybody,
>
> I am using a 3-node Cassandra cluster with Cassandra 3.0.10.
>
> I recently added a new node (to make it a 3-node cluster).
>
> I am using a replication factor of 3 , so I expected to have a copy of
> the same data on each node :
>
> CREATE KEYSPACE mydata WITH replication = {'class': 'SimpleStrategy',
> 'replication_factor': '3'}  AND durable_writes = true;
>
> But the new node has  less data that the other 2 :
>
> Datacenter: datacenter1
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> --  Address   Load   Tokens   Owns (effective)  Host
> ID   Rack
> UN  XXX.XXX.XXX.XXX  53.28 GB   256  100.0% xx  rack1
> UN  XXX.XXX.XXX.XXX  64.7 GB256  100.0% xx  rack1
> UN  XXX.XXX.XXX.XXX  1.28 GB256  100.0% xx  rack1
>
>
> On the new node :
>
> /XX/data-6d674a40efab11e5b67e6d75503d5d02/:
> total 1.2G
>
> on one of the old nodes :
>
> /XX/data-6d674a40efab11e5b67e6d75503d5d02/:
> total 52G
>
>
> I am monitoring the amount of data on each node, and they grow at the
> same rate. So I suspect that my new data are replicated on the 3 nodes
> but the old data stored on the first 2 nodes are not replicated on the
> new node.
>
> I ran nodetool repair (on each node, one at a time), but the new node
> still does not have a copy of the old data.
>
> Could you please help me understand why the old data is not replicated
> to the new node ? Please let me know if you need further information.
>
> Thank you,
>
> Cheers,
>
> Bertrand
>
>

data not replicated on new node

[Bertrand Brelier]

Hello everybody,

I am using a 3-node Cassandra cluster with Cassandra 3.0.10.

I recently added a new node (to make it a 3-node cluster).

I am using a replication factor of 3 , so I expected to have a copy of 
the same data on each node :


CREATE KEYSPACE mydata WITH replication = {'class': 'SimpleStrategy', 
'replication_factor': '3'}  AND durable_writes = true;


But the new node has  less data that the other 2 :

Datacenter: datacenter1
===
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
--  Address   Load   Tokens   Owns (effective)  Host 
ID   Rack

UN  XXX.XXX.XXX.XXX  53.28 GB   256  100.0% xx  rack1
UN  XXX.XXX.XXX.XXX  64.7 GB256  100.0% xx  rack1
UN  XXX.XXX.XXX.XXX  1.28 GB256  100.0% xx  rack1


On the new node :

/XX/data-6d674a40efab11e5b67e6d75503d5d02/:
total 1.2G

on one of the old nodes :

/XX/data-6d674a40efab11e5b67e6d75503d5d02/:
total 52G


I am monitoring the amount of data on each node, and they grow at the 
same rate. So I suspect that my new data are replicated on the 3 nodes 
but the old data stored on the first 2 nodes are not replicated on the 
new node.


I ran nodetool repair (on each node, one at a time), but the new node 
still does not have a copy of the old data.


Could you please help me understand why the old data is not replicated 
to the new node ? Please let me know if you need further information.


Thank you,

Cheers,

Bertrand

CASSANDRA-8488 status

[Vova Shelgunov]

Dear Community,

What is the current status of CASSANDRA-8488
 ticket?

In my application, I need to do such filtering inside a partition.

Regards,
Uladzimir

Is Centos 7 Supported for Version 3.0

[Shalom Sagges]

Hi Guys,

A simple question for which I couldn't find an answer in the docs.
Is Centos 7 supported on DataStax Community Edition v3.0.9?

Thanks!


Shalom Sagges
DBA
T: +972-74-700-4035
 
 We Create Meaningful Connections


-- 
This message may contain confidential and/or privileged information. 
If you are not the addressee or authorized to receive this on behalf of the 
addressee you must not use, copy, disclose or take action based on this 
message or any information herein. 
If you have received this message in error, please advise the sender 
immediately by reply email and delete this message. Thank you.

Re: Storing videos in cassandra

[vvshvv]

I have a requirement to store images of different sizes somewhere and display images of same size in grid (up to 50), and looking at Pithos architecture, relatively large files will be divided in small chunks and they will not be combined into one file quickly.



Sent from my Mi phoneOn Benjamin Roth , Nov 20, 2016 1:06 PM wrote:I haven't had the chance to test Pithos but from an architectural view it MUST be slower than a haystack-like architecture (https://code.facebook.com/posts/685565858139515/needle-in-a-haystack-efficient-storage-of-billions-of-photos/). This is why we decided to move to SeaweedFS (https://github.com/chrislusf/seaweedfs). It still has a central component (master server) but it is so slim and well designed that you really need to hit a Facebook-like scale to push it to the limits. Haystack is purely designed for simplicity + speed.If you need more functionality, like authentication, permission management, multi-tenancy, whatever, it probably will not be the architecture of your choice. Actually there are really a lot of solutions for a Blob-Store. Some use Cassandra, many of them have different approaches, every one with its own pros and cons for certain use cases.2016-11-20 10:53 GMT+01:00 DuyHai Doan :No idea, just contact themOn Sun, Nov 20, 2016 at 5:45 AM, vvshvv  wrote:Hi Doan,

Is there any performance test of Pithos? 



Sent from my Mi phoneOn DuyHai Doan , Nov 19, 2016 6:46 PM wrote:There is a project Pithos that stores blob in Cassandra and exposes them via S3 compatible API:https://www.exoscale.ch/syslog/2016/08/15/object-storage-cassandra-pithos/On Sat, Nov 19, 2016 at 1:36 PM, Kai Wang  wrote:IIRC, I watched a presentation where they said Netflix store almost everything in C* *except* video content and payment stuff.
That was 1-2 years ago. Not sure if it's still the case.
On Nov 14, 2016 12:03 PM, "raghavendra vutti"  wrote:Hi, Just wanted to know How does hulu or netflix store videos in cassandra.Do they just use references to the video files in the form of URL's and store in the DB??could someone please me on this.Thanks,Raghavendra.



-- Benjamin RothProkuristJaumo GmbH · www.jaumo.comWehrstraße 46 · 73035 Göppingen · GermanyPhone +49 7161 304880-6 · Fax +49 7161 304880-1AG Ulm · HRB 731058 · Managing Director: Jens Kammerer

Re: Storing videos in cassandra

[Benjamin Roth]

I haven't had the chance to test Pithos but from an architectural view it
MUST be slower than a haystack-like architecture (
https://code.facebook.com/posts/685565858139515/needle-in-a-haystack-efficient-storage-of-billions-of-photos/).
This is why we decided to move to SeaweedFS (
https://github.com/chrislusf/seaweedfs). It still has a central component
(master server) but it is so slim and well designed that you really need to
hit a Facebook-like scale to push it to the limits. Haystack is purely
designed for simplicity + speed.
If you need more functionality, like authentication, permission management,
multi-tenancy, whatever, it probably will not be the architecture of your
choice. Actually there are really a lot of solutions for a Blob-Store. Some
use Cassandra, many of them have different approaches, every one with its
own pros and cons for certain use cases.

2016-11-20 10:53 GMT+01:00 DuyHai Doan :

> No idea, just contact them
>
> On Sun, Nov 20, 2016 at 5:45 AM, vvshvv  wrote:
>
>> Hi Doan,
>>
>> Is there any performance test of Pithos?
>>
>>
>>
>> Sent from my Mi phone
>> On DuyHai Doan , Nov 19, 2016 6:46 PM wrote:
>>
>> There is a project Pithos that stores blob in Cassandra and exposes them
>> via S3 compatible API:
>>
>> https://www.exoscale.ch/syslog/2016/08/15/object-storage-
>> cassandra-pithos/
>>
>> On Sat, Nov 19, 2016 at 1:36 PM, Kai Wang  wrote:
>>
>>> IIRC, I watched a presentation where they said Netflix store almost
>>> everything in C* *except* video content and payment stuff.
>>>
>>> That was 1-2 years ago. Not sure if it's still the case.
>>>
>>> On Nov 14, 2016 12:03 PM, "raghavendra vutti" <
>>> raghu9raghaven...@gmail.com> wrote:
>>>
 Hi,

  Just wanted to know How does hulu or netflix store videos in cassandra.

 Do they just use references to the video files in the form of URL's and
 store in the DB??

 could someone please me on this.


 Thanks,
 Raghavendra.











>>
>


-- 
Benjamin Roth
Prokurist

Jaumo GmbH · www.jaumo.com
Wehrstraße 46 · 73035 Göppingen · Germany
Phone +49 7161 304880-6 · Fax +49 7161 304880-1
AG Ulm · HRB 731058 · Managing Director: Jens Kammerer

Re: Storing videos in cassandra

[DuyHai Doan]

No idea, just contact them

On Sun, Nov 20, 2016 at 5:45 AM, vvshvv  wrote:

> Hi Doan,
>
> Is there any performance test of Pithos?
>
>
>
> Sent from my Mi phone
> On DuyHai Doan , Nov 19, 2016 6:46 PM wrote:
>
> There is a project Pithos that stores blob in Cassandra and exposes them
> via S3 compatible API:
>
> https://www.exoscale.ch/syslog/2016/08/15/object-storage-cassandra-pithos/
>
> On Sat, Nov 19, 2016 at 1:36 PM, Kai Wang  wrote:
>
>> IIRC, I watched a presentation where they said Netflix store almost
>> everything in C* *except* video content and payment stuff.
>>
>> That was 1-2 years ago. Not sure if it's still the case.
>>
>> On Nov 14, 2016 12:03 PM, "raghavendra vutti" <
>> raghu9raghaven...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>>  Just wanted to know How does hulu or netflix store videos in cassandra.
>>>
>>> Do they just use references to the video files in the form of URL's and
>>> store in the DB??
>>>
>>> could someone please me on this.
>>>
>>>
>>> Thanks,
>>> Raghavendra.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>