Hi,
I have a second index on a static column and I don't
understand the answer I get from my select.
Maybe someone who understands the inner working of the second index can
give me a hint on this (cassandra 3.9)
A cut down version of the table is:
create table demo (id text, id2 bigint static,
Hi,
my cluster is quite new, with three (jessie) nodes and only some test
tables with a few rows of data in it.
I just started a fresh one-node-cluster on another machine, created the
table then the second index on the static column and inserted one row of
data.
create table demo (id text, adde
Hi,
forget my the last mail. On the single node cluster it works.
I can try it on the three-node cluster with a keyspace with replication
factor of 1 and see what happens.
I left most of the default config of cassandra untouched, except storage
directories and ip addresses.
Cheers,
Michael
I have restarted the three node cluster with new directories for data
and commitlog and made the test again.
This time the resultset size is 62 rows for the select.
If I execute the select often it jumps between 62 and 65 rows.
After inserting a second row I get 129 rows back I select using the i
OK, thanks, that was good!
You have allocated the keyspace with replication factor 3. If I do this
it works on my cluster too!
If I try this in a new keyspace with replication factor 2 I get the same
result as before, nearly at least, this time 58 rows.
I can reproduce this: 3-node cluster and r
Hi,
with cqlsh running on one of the cluster machines I get the following
error when issuing
use my_keyspace;
copy demo to stdout;
Error:
() got an unexpected keyword argument 'encoding'
Seems like a python driver issue.
Whereas, if I start cqlsh in debug mode, the export works without errors.
I use "copy from" to import a bunch of csv files, each with 100 rows
(exported by "copy to" from another table)
There is a chance that the copy from just hangs, after importing 9995000
lines, doing nothing, waiting forever.
Could this be a race in the copy code? I use NUMPROCESSES=6, in bash
Hello,
when calling sstabledump from cassandra 3.11 I get the error:
"There is an incompatible JNA native library installed on this system
Expected: 5.1.0
Found: 4.0.0"
Maybe I overlooked something, but after searching I found the newest
version to be 4.4 with 4.5 the upcoming new version.
My
Debian jessie, cassandra 3.11 binary debian install (which comes from
dl.bintray.com/apache/cassandra/ )
apt-cache policy shows that the version of the jna lib is 4.1.0
java 8 is a backport for jessie.
(not 4.0.0 , which is shown by sstabledump)
Cassandra itself doesn't show any error about jna
Michael
On 18.07.2017 13:36, Stefan Podkowinski wrote:
> I haven't been able to reproduce this on Ubuntu or CentOS. Which OS do
> you use? Did you install a pre-build package or tarball?
>
> On 18.07.2017 11:43, Micha wrote:
>> Hello,
>>
>> when calling ss
Hi,
I added a fourth node to my cluster, after the boostrap I changed RP
from 2 to 3 and ran nodetool repair on the new node.
A few hours later the repair command exited with the
UndeclaredThrowableException and the node was down.
In the logs I don't see a reason for the exception or shutdown.
Hi,
it seems I'm not able to add add 3 node dc to a 3 node dc. After
starting the rebuild on a new node, nodetool netstats show it will
receive 1200 files from node-1 and 5000 from node-2. The stream from
node-1 completes but the stream from node-2 allways fails, after sending
ca 4000 files.
Afte
hael
On 11.08.2017 01:25, Jeff Jirsa wrote:
>
>
> On 2017-08-08 01:00 (-0700), Micha wrote:
>> Hi,
>>
>> it seems I'm not able to add add 3 node dc to a 3 node dc. After
>> starting the rebuild on a new node, nodetool netstats show it will
>> receive 1
the nodes have 32G ram, there are no other processes running.
Thanks for the info about the g1gc.
I used bootstrap resume to finish the bootstrap, then added another two
nodes.
This worked, but I saw in munin a constantly rising memory consumption
during streaming, while on the other nodes there w
Hi,
I started a repair (7 nodes, C* 3.11) but at once I get an exception in
the log:
"RepairException: [# on keyspace/table, [],
Validation failed in /ip"
The started nodetool repair hangs (the whole day...), strace shows it's
waiting...
What's the reason for this excpetion and what to
exander Dejanovski wrote:
> Hi Micha,
>
> Are you running incremental repair ?
> If so, then validation fails when 2 repair sessions are running at the same
> time, with one anticompacting an SSTable and the other trying to run a
> validation compaction on it.
>
> If you
ok, thanks, so I don't use the -pr option anymore (I used it on the
first node). It seems to take some time. running for 150minutes to
complete 7% ...
Cheers,
Michael
On 14.09.2017 15:40, Alexander Dejanovski wrote:
> There should be no migration needed, but if you have a lot of data,
> antic
Hi,
I get the following exception during repair. After some of these are
thrown, the cassandra node shuts down. Now I don't know how to get
things working again.
A few days ago there were errors due to a column being much too big.
This is fixed but could this be the reason for this, some corrupt
Hi,
I have seven nodes, debian stretch with c*3.11, each with 2TB disk (500G
free), 32G Ram.
I have a keyspace with seven tables. At the moment the cluster doesn't
work at all reliably. Every morning at least 2 nodes are shut down due
to out of memory. Repair afterwards fails with "some repair fai
Hi,
after 135 min a "nodetool repair -pr .." failed with "Some repair failed"
Is there a possibility to find out what exactly failed?
The log states "repair command #1 finished in ..."
What to do now? Just start again and hope that it will finish this time
successfully?
thanks
Michael
-
20 matches
Mail list logo
