I had problems with write_survey.
I opened a bug : https://issues.apache.org/jira/browse/CASSANDRA-9934
De : horschi [mailto:hors...@gmail.com]
Envoyé : mardi 4 août 2015 15:20
À : user@cassandra.apache.org
Objet : Re: auto_bootstrap=false broken?
Hi Paulo,
thanks for your feedback, but I
Do you see this log message?
logger.infohttp://logger.info(Startup complete, but write survey mode is
active, not becoming an active ring member. Use JMX
(StorageService-joinRing()) to finalize ring joining.);
ð Yes !
Log : INFO [main] 2015-07-29 15:29:35,697 StorageService.java (line
Hello,
I start a node with the write survey = true
-Dcassandra.write_survey=true
Log:
INFO [main] 2015-07-29 15:29:35,697 StorageService.java (line 853) Startup
complete, but write survey mode is active, not becoming an active ring member.
Use JMX (StorageService-joinRing()) to finalize ring
Hello,
If current CL = ONE, Be careful on production at the time of change replication
factor, 3 nodes will be queried while data is being transformed ==> So data
read errors!
De : Yulian Oifa [mailto:oifa.yul...@gmail.com]
Envoyé : jeudi 5 novembre 2015 16:02
À : user@cassandra.apache.org
Thx Carlos,
How can I get information on error during repair ?
Thx.
De : Carlos Alonso [mailto:i...@mrcalonso.com]
Envoyé : lundi 19 octobre 2015 11:09
À : user@cassandra.apache.org
Objet : Re: management and monitoring nodetool repair
So repair process has two phases:
First one is all about
Hi,
I'm looking for a tool for management and monitoring of the status of nodetool
repair.
Currently I am trying to test cassandra-reaper, but if you tested other tools
thank you to share.
Thanks
Hi,
I'm trying to insert data with Cassandra-stress into cluster C* with 6 nodes:
node001006
The stress-tool is executed on a different machine (gen01) specifying one of 6
nodes: tools/bin/cassandra-stress user profile=cf.yml ops\(insert=1\)
n=500 -mode thrift -node node001 -rate
Hi all,
Does compaction throughput impact write performance ?
Increasing the value of compaction_throughput_mb_per_sec can improve the insert
data ? If yes, is it possible to explain to me the concept ?
Thanks.
Hello,
> First, Is this data modeling correct for follow base (follower,
following actions) social network?
For social network, I advise you to see Graph Databases, over Cassandra
Example : https://academy.datastax.com/resources/getting-started-graph-databases
De : Mohammad Kermani
Hello,
I read in the documentation DataStax :
"The coordinator node might also need to work hard to process a logged batch
while maintaining consistency between tables"
It means that the coordinator send the mutations to all replica nodes and
waits for RF acknowledgements ? or only one node
I need to query all columns by the userid.
For example: Select * from users where userid = 123;
frozen UDT don’t exist in Cassandra 2.0 ☹
De : Jack Krupansky [mailto:jack.krupan...@gmail.com]
Envoyé : jeudi 28 janvier 2016 16:38
À : user@cassandra.apache.org
Objet : Re: Modeling nested
Thank you !
Another question please : In the blog post
(http://www.datastax.com/dev/blog/off-heap-memtables-in-Cassandra-2-1), it is
noted that offheap_objects it effective for small values like ints or uuids as
well. offheap_buffers for the tables with string or blobs.
in my case, the tables
Hello,
I try to insert two lines for the same partition with the same timestamp.
prmiere the line without TTL. the 2nd line with TTL.
As shown in the example below:
INSERT INTO tab1 (a,b) VALUES ('YYY','') USING TIMESTAMP 1460088862025940
INSERT INTO tab1 (a,b) VALUES ('YYY','') USING
Hi,
offheap_objects was removed in releases 3.2.x then reintroduced in release
3.4: I vould like to know if someone has used offheap_objects in Cassandra 2.1:
stable or not, improvement observed or not...
Thanks.
Ahmed
full is a reserved word in apache Cassandra / cql 3.1
https://cassandra.apache.org/doc/cql3/CQL.html#appendixA
*Reserved keywords cannot be used as identifier , they are truly reserved for
the language (but one can enclose a reserved keyword by double-quotes to use it
as an identifier)
De :
Hi,
We recently got an exception during compaction on some nodes (Cassandra
2.1.14):
ERROR [CompactionExecutor:14065] 2016-12-30 14:45:07,245
CassandraDaemon.java:229 - Exception in thread
Thread[CompactionExecutor:14065,1,main]
java.lang.IllegalArgumentException: Not enough bytes. Offset:
16 matches
Mail list logo