Thanks you for your replies so far. We are just going to .14 because our repair
is consuming cpu and our management always want to to stay a couple version
behind for stability reasons.
Sent from my iPhone
> On Mar 23, 2018, at 4:50 PM, Jeff Jirsa wrote:
>
> Why .14? I would consider 3.0.16 t
Why .14? I would consider 3.0.16 to be production worthy.
--
Jeff Jirsa
> On Mar 23, 2018, at 2:01 PM, Nitan Kainth wrote:
>
> Hi All,
>
> Our repairs are consuming CPU and some research shows that moving to 3.0.14
> will help us fix them. I just want to know community's experience about
>
3.0.16 is the latest, I recommend going all the way up. About a hundred
bug fixes:
https://github.com/apache/cassandra/blob/cassandra-3.0/CHANGES.txt
Jon
On Fri, Mar 23, 2018 at 2:22 PM Dmitry Saprykin
wrote:
> Hi,
>
> I successfully used 3.0.14 more than a year in production. And moreover
> 3
Hi,
I successfully used 3.0.14 more than a year in production. And moreover
3.0.10 is definitely not stable and you need to upgrade ASAP. 3.0.10
contains known bug which corrupts data during schema changes
Regards,
Dmitrii
On Fri, Mar 23, 2018 at 5:01 PM Nitan Kainth wrote:
> Hi All,
>
> Our r
Hi All,
Our repairs are consuming CPU and some research shows that moving to 3.0.14
will help us fix them. I just want to know community's experience about
3.0.14 version.
Is it stable?
Anybody had any issues after upgrading this?
Regards,
Nitan K.
