just to share with you, by running rebuild_index the problem is solved.
2016-08-11 22:05 GMT+02:00 Adil :
> After migrating C* from 2.1.2 to 3.0.8, all queries with the where
> condition involved ad indexed column return zero rows for the old data,
> instead news inserted data are returned from t
After migrating C* from 2.1.2 to 3.0.8, all queries with the where
condition involved ad indexed column return zero rows for the old data,
instead news inserted data are returned from the same query, I'm guessing
that something was remained incomplete about indexes, should we run rebuild
indexes? A
Thank you for your response, we have updated datastax driver to 3.1.0 using
V3 protocol, i think there are still some webapp that still using the 2.1.6
java driver..we will upgrade thembut we noticed strange things, on web
apps upgraded to 3.1.0 some queries return zero results even if data
exi
Another thing to note is that according to NEWS.txt upgrade from 2.1.x is
only supported from version 2.1.9, so if this is not an effect of that I'm
actually surprised upgrade from 2.1.2 worked without any issues.
2016-08-10 15:48 GMT-03:00 Tyler Hobbs :
> That just means that a client/driver dis
That just means that a client/driver disconnected. Those log messages are
supposed to be suppressed, but perhaps that stopped working in 3.x due to
another change.
On Wed, Aug 10, 2016 at 10:33 AM, Adil wrote:
> Hi guys,
> We have migrated our cluster (5 nodes in DC1 and 5 nodes in DC2) from
>
Hi guys,
We have migrated our cluster (5 nodes in DC1 and 5 nodes in DC2) from
cassandra 2.1.2 to 3.0.8, all seems fine, executing nodetool status shows
all nodes UN, but in each node's log there is this log error continuously:
java.io.IOException: Error while read(...): Connection reset by peer
at
