Micha,
I did not had the time to look into your problem yet.
Could you open a JIRA ticket to be sure that we do not forget about this
problem? I will look into it as soon as I can.
On Mon, Jan 30, 2017 at 5:12 PM, Benjamin Lerer wrote:
> I do not see why you should get that problem with a repli
I do not see why you should get that problem with a replication factor of 2.
I will look into it.
On Mon, Jan 30, 2017 at 5:06 PM, Micha wrote:
> 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
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
So, far I do not have any sucess in trying to reproduce the problem.
I created a 3 node clusters using 3.9 with ccm and used CQLSH to reproduce
the problem but I only got back one row:
cqlsh> create KEYSPACE test WITH replication = {'class': 'SimpleStrategy',
'replication_factor': 3};
cqlsh> use
I will try to reproduce the problem.
Thanks for the information
On Mon, Jan 30, 2017 at 2:34 PM, Micha wrote:
> 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 execut
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
Sorry,
I am not sure that I understand you correctly. Do you see the problem on a
one Node cluster or not?
On Mon, Jan 30, 2017 at 12:05 PM, Micha wrote:
> 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 repl
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
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 Michael,
It sound like a bug but I could not reproduced it on 3.9 or on the current
3.11 branch (which will become 3.10).
Now, that does not mean that there are not problem. Something might be
different in your environement.
Do you still see that problem when you start from a clean environment
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,
11 matches
Mail list logo
