Hello,
We have a 6 node cluster which was recently upgraded from 2.2.5 to 3.0.10.
Since then, we have been facing a lot of these exceptions. What could be the
possible cause for this exception?
INFO [SharedPool-Worker-2] 2017-02-23 20:14:04,984 Message.java:611 -
Unexpected exception during r
Is ver 3.0.10 same as 3.10.
Cassandra website mentions this: Cassandra 3.10 Changelog
But in other places 3.0.10 is mentioned.
No
> On Feb 23, 2017, at 1:59 PM, Rakesh Kumar wrote:
>
> Is ver 3.0.10 same as 3.10.
>
> Cassandra website mentions this: Cassandra 3.10 Changelog
>
> But in other places 3.0.10 is mentioned.
> Is ver 3.0.10 same as 3.10.
They are different. In particular:
- 3.0.10 contains the features in versions 3.0.0, but with bugfixes.
It's the next in the series of 3.0.0, 3.0.1, 3.0.2, and so on to 3.0.9
and 3.0.10. Typically, 3.0.X releases don't add major features,
instead being smaller bugfix
Hey,
Any reasons why old versions get removed from the Debian repository when a new
version gets promoted?
For instance, here one would expect to still be able to:
$ apt-get install cassandra=3.0.10
But after that release only the latest 3.0.11 is available:
http://dl.bintray.com/apache
This is correct, we use reprepro and leave the old versions in the pool.
I'm not exactly sure what you mean by "put them back to the apt cache",
Julien. The only thing needed for a downgrade is:
`wget $URL && dpkg -i cassandra*.deb`
If you run lots of servers on a specific version, then I'd sug
Hi All,
In my application sometimes I cannot read data that just got inserted. This
happens very intermittently. Both write and read use LOCAL QUOROM.
We have a cluster of 12 nodes which spans across 2 Data Centers and a RF of 3.
Has anyone encountered this problem and if yes what steps have y
Have you checked that NTP is correctly synched across all nodes in your
cluster?
On Fri, 24 Feb 2017 at 17:29 Charulata Sharma (charshar)
wrote:
>
> Hi All,
>
> In my application sometimes I cannot read data that just got inserted.
> This happens very intermittently. Both write and read use LOCA
