reate tombstones since the ttl is present together with the write
time timestmap
at the row level
Greetings
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
Yes, I can see. Looks like cluster got overcharged and full repair was
running, we got to restart all nodes and it seems to fix the problem. We
will upgrade version soon
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Mar 17, 2022 at 5:12 PM
.
Is there an issue with this version ?
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
, I got the same error with
INFO [OptionalTasks:1] 2021-12-16 04:41:34,078
CassandraRoleManager.java:432 - Setup task failed with error, rescheduling
org.apache.cassandra.exceptions.IsBootstrappingException: Cannot read from
a bootstrapping node
Thanks
Jean Carlo
"The best way to predic
you have your cluster well balanced with 32
tokens. 32 tokens seems to be the future default value, but changing the
default vnodes token numbers seems not to be so straight forward
cheers
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Sat, Jan 25, 2020
Hello
Nobody has mentioned but you can use spark cassandra connector also.
Preferably if your data set is so big that a simple copy to csv cannot
handle it
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Fri, Jan 17, 2020 at 8:11 PM Durity, Sea
Hello Laxmiant,
your application has to deal with eventually consistency if you are using
cassandra. Ensure to have
R + W > RF
And have the repairs runing periodically. This is the best way to be the
most cosistent and coherent
Jean Carlo
"The best way to predict the future is to i
Concerning to "Starting listening for CQL clients" message, once you get
it, you will be able to do cqlsh, so both of them are the same
Cheers
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Jan 9, 2020 at 9:14 AM wrote:
> I've alwa
sync
amongs DC after you have run the repair. But if you still want to do it,
use Spark for it.
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Wed, Aug 21, 2019 at 1:51 PM Rahul Reddy
wrote:
> Yep I did run rebuild on each new node
>
> On Wed,
Hello Voytek,
In my opinion, It would be better for you to continue using
GossipingPropertyFileSnitch in AWS as well. I would do it to avoid
surprises. I've set up datacenters in AWS using GossipingPropertyFileSnitch
with zero problems.
Jean Carlo
"The best way to predict the fu
t;
What is the interest to use allocate_tokens_for_keyspace in a cluster with
data if there tokens are already distributed? in the worst case scenario,
the cluster is already unbalanced
Cheers
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Mon, Apr
DynamicEndPointSnitch: enabled
Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
Schema versions:
3bf63440-fad7-3371-9c14-4855ad11ee83: [192.0.0.1, 192.0.0.2]
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Jan 24, 2019 at 10:3
I think this jira
https://issues.apache.org/jira/browse/CASSANDRA-9895
Answer my question
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Fri, Apr 12, 2019 at 10:04 AM Jean Carlo
wrote:
> Hello Sean
>
> Well this is a little bit confu
evel.
>
> Like this:
>
> cluster.setQueryOptions(new
> QueryOptions().setConsistencyLevel(ConsistencyLevel.valueOf(cassandraConsistencyLevel)));
>
>
>
> The only possibility i see of such behavior is its getting overridden from
> some where.
>
>
>
> Tha
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
In my cluster, I have it at 4096. I think you can start with 1024 and check
if you have no native requested blocked.
I believe this parameter depends on the cluster traffic
Cheers
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Apr 9, 2019 at 7:5
Awesome
Thank you very much
Cheers
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Mar 5, 2019 at 2:47 PM Jeff Jirsa wrote:
>
>
>
> > On Mar 5, 2019, at 5:32 AM, Jean Carlo
> wrote:
> >
> > Hello Jeff, thank
?
Thank you ?
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Mar 5, 2019 at 2:24 PM Jeff Jirsa wrote:
> Ec2 multi should work fine in one region, but consider using
> GossipingPropertyFileSnitch if there’s even a chance you’ll want something
Ec2MultiRegionSnitch is inevitable
Thank you
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
Hello,
I find this discussion very useful. I did not see information about this
topic in cassandra apache web page. Shouldn't we have a instruction page to
create a new fresh cluster following the right instructions to use
correctly the option allocate_tokens_for_keyspace ?
Jean Carlo
Hi Victor,
Take a look to this jira
https://issues.apache.org/jira/browse/CASSANDRA-13701
I may answer your questions
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Mon, Jan 21, 2019 at 12:08 PM VICTOR IBARRA wrote:
>
> Good morning every
Hello,
Can I ask you why did you upgrade from 3.11.2 ? did you experience some
java heap problems ?
Unfortunately I cannot answer your question :( I am in the 2.1 and about to
upgrade to 3.11
Best greatings
Jean Carlo
"The best way to predict the future is to invent it" Alan Ka
cluster.
Actually, I want to know if cassandra_range_repair works properly in 3.11
because its repository is not active so far
Best greetings
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
k you very much
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
Thank you ahmed!
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Jun 28, 2018 at 11:21 AM, Ahmed Eljami
wrote:
> Hello Jean Carlo,
>
> To activate Debug mode, you should edit "logback.xml " not
> "log4j-server.properties"
>
>
> Ahmed.
>
result
Thx
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
ks for the versions 3.11.2. And I will take a look also to
cassandra_range_repair
<https://github.com/BrianGallew/cassandra_range_repair> which it is more
recent
Do you have any remarks for cassandra-list-subranges
<https://github.com/pauloricardomg/cassandra-list-subranges> ?
S
s with the options -pr -full
Anyone knows why does cassandra make those anticompactions ?
Thanks
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
copy to.
and in the step 6 copy the sstables to the right directory corresponding to
the tale you want to copy to.
Be sure you have an snapshot of the table source and ignore step 4 of
course
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On
Hello,
Talking about heap pressure, is there any difference between make a '*select
**' and a '*select field *'?
Is cassandra taking into the heap the whole partition to make the merge
doesn't matters if we make a select of few rows ?
Best greatings
Jean Carlo
&qu
confirm I am
missing something
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Feb 22, 2018 at 10:28 PM, Kenneth Brotman <
kenbrot...@yahoo.com.invalid> wrote:
> I will heavy lift the docs for a while, do my Slender Cassandra reference
f there's no data in the first DC, you can
skip a couple steps and just leave it on.
Leave it on, and enjoy your afternoon.
Seeds don't bootstrap by the way, changing the setting on those nodes
doesn't do anything.
On Thu, Feb 22, 2018 at 8:36 AM Jean Carlo
wrote:
> Hello
&g
s not better to bootstrap first the seeds with auto_bootstrap: false
and then the rest of the nodes with auto_bootstrap: true ?
Thank you for the help
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
Hi Marcus
>java version ?
We use oracle-java8-jre the version 8u92.
>TLSv1 disabled ?
No it is not disable. We tried also with the version 1.2
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Wed, Jan 31, 2018 at 12:11 PM, Marcus
having the 'SSL
peer shut down incorrectly' error. Anyone have had this error before?
best greetings
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
complete keyspace
system node by node.
So you will have the same cluster( cluster name, confs, etc)
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Jan 11, 2018 at 10:28 AM, Pradeep Chhetri
wrote:
> Hello Jean,
>
> I am running cassandra
sstable node by
node, it would be enough to make nodetool refresh in every node to restore
your data. You can also restart casandra instead of doing nodetool refresh.
It will help you to avoid the compactions after refreshing.
Saludos
Jean Carlo
"The best way to predict the future is to inve
em keyspace
> snapshots.
>
> Regards,
> Anthony
>
> On 16 October 2017 at 23:28, Jean Carlo wrote:
>
>> HI,
>>
>> Yes of course, you can use sstableloader from every sstable to your new
>> cluster. Actually this is the common procedure. Just check the l
es, I believe you can just copy and paste your data node
per node and make a nodetool refresh. Checking obviously the correct names
of your sstables.
You can check the tokens of your node using nodetool info -T
But I think sstableloader is the easy way :)
Saludos
Jean Carlo
"The b
e
the topology file (cassandra-topology.properties).
Or it is possible ? That's why you mentioned (firewall rules are helpful
here) isn't it?
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Mon, Oct 16, 2017 at 5:29 AM, kurt greaves
Hi,
Be sure that you have the same tokens distribution than your original
cluster. So if you are going to restore from old node 1 to new node 1, make
sure that the new node and the old node have the same tokens.
Saludos
Jean Carlo
"The best way to predict the future is to invent it"
keyspace is rf 3 and I have 3 racks
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
new tokens ranges from the existing ones.
it could lead to some tokens being owned by two nodes, am I right ?
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Fri, Sep 29, 2017 at 1:21 PM, Jacob Shadix wrote:
> Are you building out a new DC?
>
keyspace ?
Best greetings
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
Hello community,
I am analysing a dump of 11GB and I am using eclipse memory analyser.
I would like to know if you guys really need a machine with 32GB to analyse
a dump of G1GC of 30GB or there is another smarter way to do that.
Greetings
Jean Carlo
"The best way to predict the future
see that and I would like to
understand.
Cassandra only take this change in account when we use the option
JVM_OPTS="$JVM_OPTS -Dcassandra.load_ring_state=false"
Why doesn't cassandra take in account the new list of seeds in the ossipDigest?
Saludos
Jean Carlo
"The bes
OutboundTcpConnection.java:496 - Cannot handshake version with /10.0.0.143
INFO [HANDSHAKE-/10.0.0.143] 2017-07-04 10:29:50,090
OutboundTcpConnection.java:487 - Handshaking version with /10.0.0.143
Is it enough to solve by restarting cassandra both nodes ?
Best regards
Jean Carlo
"The best way to pr
Hello.
What if a node send a merkle tree to its replica but this one would never
received by any network issues. The repair will be hanging eternally ? or
Should I modify the parameter
# streaming_socket_timeout_in_ms: 0 to avoid this ?
Saludos
Jean Carlo
"The best way to predict the f
Hello
In cassandra 2.1. When a replica has sent its merkle tree, Does it via
streaming ? which protocol does it use ?
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
same time I can see that the duration of GC has increased also
There is a link between the increasment of the GC and the bloom filter ?
Jean Carlo
Hello
the jira 12849 has already a patch dispo. Might someone take a look of this
jira ?
https://issues.apache.org/jira/browse/CASSANDRA-12849
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
LCS to LCS this is not pertinent
In my case, I use nodetool refresh not only to restore a table but also to
make an exact copy of any table LCS. So I think the levels do not need to
change.
@Marcus Can you be so kind to clarify this for me please ?
Thenk you very much in advance
Best regards
Jean
Hello @Durity
Would you mind to share information about your cluster? Actually I am
interested to know which version of cassandra you use. And how much time do
the gc pauses spend.
Thank you very much
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan K
I think it is wise to add them one by one. taking in account that the
cluster must re arrange the tokens among the replicas.
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Jan 24, 2017 at 12:00 PM, Andreas Fritzler <
andreas.fritz...@gma
the ratio is 0.17053810600081237
SSTable Compression Ratio: 0.17053810600081237
Then my actual size of data uncompressed is 0.17053810600081237 x 34GB ~~
200GB which makes sense :)
Nice to know the subtlenes of cassandra :)
Saludos
Jean Carlo
"The best way to predict the future
has only 34GB
of data.
Best greetings
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
isn't the expected behavior.
Did anyone get the same behavior ?
<https://github.com/apache/cassandra/blob/cassandra-2.1/debian/init>
Best regards
Jean Carlo
"The best way to predict the future is to inven
<https://github.com/apache/cassandra/blob/cassandra-2.1/debian/init>t it"
Alan Kay
Yes, we did it.
So if the parameter in cassandra-env.sh is used only if we have a OOM, what
is for the definition of
*-XX:HeapDumpPath=/var/lib/cassandra/java_1475461286.hprof
*in /etc/init.d/cassandra for?
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Al
andra-env.sh?
Anyone any idea?
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Mon, Oct 3, 2016 at 12:00 PM, Jean Carlo
wrote:
>
> Hi
>
> I see in the log of my node cassandra that the parameter -XX:HeapDumpPath
> is charged two times.
have to dump the heap because cassandra uses
the disk not suitable to do it.
Is *XX:HeapDumpPath *set in another place/file that I dont know?
Thxs
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
hat this has only partial
support for incremental repair due to CASSANDRA-10422 and should not mark
sstables as repaired, so you could be hitting CASSANDRA-12489.
Thx Paulo :)
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Mon, Sep 12, 2016 at 2:
isn't 0). Well just those sstables not
sync.
So my quesion is, if we migrate to repair inc in prod and we dont use the
migration procedure, for tables that some sstables are never mutated, they
will keep in a not repaired state ?
Probably there is something I am not able to see
Saludos
J
Hi @Bryan
When you said "sizable amount of data" you meant a huge amount of data
right? Our big table is in LCS and if we use the migration process we will
need to run a repair seq over this table for a long time.
We are planning to go to repairs inc using the version 2.1.14
Sal
.
applies for the version 2.1.14. I ask because I see that the jira
CASSANDRA-8004 is resolved for the version 2.1.2 and we are considering to
migrate to repairs inc before go to the version 3.0.x
Thhx :)
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On F
rm my assumption
Best regards.
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
Thank you very much Paulo
On Aug 5, 2016 17:31, "Paulo Motta" wrote:
> https://issues.apache.org/jira/browse/CASSANDRA-11840
>
> increase streaming_socket_timeout to 8640 or upgrade to
> cassandra-2.1.15.
>
> 2016-08-05 12:28 GMT-03:00 Jean Carlo :
>
>&g
)
~[apache-cassandra-2.1.14.jar:2.1.14]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_60]
We have this error with at least 5 more nodes in the same log. But the
error doesn't say that much
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
hread.java:745) [na:1.8.0_60]
I al looking through the changes files to see if it is a bug fixed in the
2.1.15
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Fri, Aug 5, 2016 at 4:24 PM, Paulo Motta
wrote:
> It seems you have a streamin
)
~[apache-cassandra-2.1.14.jar:2.1.14]
... 3 common frames omitted
Is it a network problem or we are having a bug ? There is nothing else in
the log of cassandra more than
Sync failed between.
We are having cassandra 2.1.14
Best regards
Jean Carlo
"The best way to predict the future
If a node is down in my cluster.
Is it possible to exclude him from the repair process in order to continue
with the repair?
If not
Is the repair continue reparing the other replicas even if one is down?
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
esManualRepair.html>
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Jun 23, 2016 at 5:34 PM, Stefano Ortolani
wrote:
> Yes, because you keep a snapshot in the meanwhile if I remember correctly.
>
> Regards,
> Stefano
>
> On
regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
etool status
- restore your previous conf of your cluster. including the node that was
down
- on the node down, if its ip address is in the list of seeds, remove it in
order to do the boobstrap
- restart cassandra in every node one by one.
It is what we do in our cluster.
Saludos
Jean Carlo
&quo
Did you use a backup of the keyspace system?
If not, you might do removenode of that node and re added to the cluster to
re generate new tokens.
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Apr 26, 2016 at 12:06 AM, ssiv...@gmail.com
wr
@Laing thx for the info.
@Carlos I also check that page and I did not find it. I was asking to know
if someone has done smth to avoid change the column name everytime
cassandra adds new words to the list.
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Al
le1 (bill_id, full, name,provider_date
,total) values ('qs','full','name','2015-02-23','toltal');
SyntaxException:
and it is because the name of the column is not longer full, is "full"
Best regards
Jean Carlo
"The best way to pr
es the result is an error
CREATE TABLE table1 ( bill_id text, * 'full' text*, name
text, provider_date timestamp, total text, PRIMARY KEY (
bill_id) ) ;
SyntaxException:
So far using double quotes doesn't resolve my problem
Saludos
Jean Carlo
"The b
;full" reserved by cassandra?
In order to not change all the configuration in production, there is a way
to conserve the name of my column as it was with the version 2.0.10?
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
However can it be nice to have the posibility to configurate that with
cassandra options, or when using a file yaml to insert data on any table.
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Mar 10, 2016 at 10:48 AM, Jean Carlo
wrote:
&
Thank you very much S. Alborghetti I will consider that suggestion.
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Thu, Mar 10, 2016 at 5:47 AM, Stefania Alborghetti <
stefania.alborghe...@datastax.com> wrote:
> On Tue, Mar 8, 2016 at
eculative_retry = '99.0PERCENTILE';
And cassandra stress create the next string to the field kvalue of type
text:
"P*d,xY\x03m\x1b\x10\x0b$\x04pt-G\x08\n`7\x1fs\x15kH\x02i1\x16jf%YM"
what bothers me is that kvalue has control characters like \x03. do you
guys know any way to a
the
process to migrate it's quite tedious if you have many nodes
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Feb 16, 2016 at 4:39 PM, Carlos Rolo wrote:
> +1 on what Alain said, but I do think if you are high enough on a 2.1.x
&g
, no compaction
were runing, even if nodetool tpstats says
CompactionExecutor
283 1424 0 0
After I restart cassandra, the comactions started to run.
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On T
283 1424
0 0
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Wed, Feb 10, 2016 at 6:00 PM, Kai Wang wrote:
> Jean,
>
> What does your cfstats look like? Especially "SSTables in each leve
that is it not possible to run sequential repair with incremental
repair at the same time.
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
Hello Horschi,
Yes I understand. Thx
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Wed, Feb 10, 2016 at 3:00 PM, horschi wrote:
> btw: I am not saying incremental Repair in 2.1 is broken, but ... ;-)
>
> On Wed, Feb 10, 2016
Hi Horschi !!!
I have the 2.1.12. But I think it is something related to Level compaction
strategy. It is impressive that we passed from 6 sstables to 3k sstable.
I think this will affect the latency on production because the number of
compactions going on
Best regards
Jean Carlo
"The
Correction:
*table cf3*
*Space used (live): 697.03 MB*
It happens that when I do repair -inc -par on theses tables, *cf3 got a
pick of 3k sstables*. When the repair finish, it takes 30 min or more to
finish all the compactations and return to 6 sstable.
Saludos
Jean Carlo
"The
to
finish all the compactations and return to 6 sstable.
I am a little concern about if this will happen on production. is it normal?
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
/trblshootIdleFirewall.html
Do you think that is ok?
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Fri, Jan 29, 2016 at 11:02 AM, Anuj Wadehra
wrote:
> Hi Jean,
>
> Please make sure that your Firewall is not dropping TCP connections whic
I am having the same issue after upgrade cassandra 2.1.12 from 2.0.10. I am
not good on jvm so I would like to know how to do what @CorryOpdenakker
propose with cassandra.
:)
I check concurrent_compactors
Saludos
Jean Carlo
"The best way to predict the future is to invent it" Al
nk it takes to much
time comparing to the write latency of ~30 microseconds.
My first clue is to fix the chunk_length_kb to a value close to the size
of the rows in kb
Am I in the right direction? If it is true, how can I compute the size of a
row?
Other question, the value of "Compacted partition" of the command nodetool
cfstats migth give me a value close to the chunk_length_kb ?
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
channel = [id: 0x3efbd844, /
172.16.162.4:9042]
Then I don't know if the firewall has something to do on that case, becasue
it is a local connection over native protocol
Best regards
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Fri, Jan 29, 2016 at 11:02 AM
the
cluster, this is not the only node that appears, acctually we are having
all the node's ip having that reset by peer problem.
Our cluster is having more reads than writes. like 50 reads per second.
Any one got the same problem?
Best regards
Jean Carlo
"The best way to predict the
94 matches
Mail list logo