Nope - I went through the logs on all nodes they look good to me - no
logged ERROR messages or exceptions.
-Jesse
On Tue, Aug 2, 2016 at 10:25 AM, Romain Hardouin
wrote:
> Just to know, did you get some errors during the nodetool upgradesstables?
>
> Romain
>
>
> Le Mardi 2 août 2016 8h40, Juli
Just to know, did you get some errors during the nodetool upgradesstables?
Romain
Le Mardi 2 août 2016 8h40, Julien Anguenot a écrit :
Hey Oskar,
I would comment and add all possible information to that Jira issue…
J.
--Julien Anguenot (@anguenot)
On Aug 2, 2016, at 8:36 AM, Oskar K
Hey Oskar,
I would comment and add all possible information to that Jira issue…
J.
--
Julien Anguenot (@anguenot)
> On Aug 2, 2016, at 8:36 AM, Oskar Kjellin wrote:
>
> Hi,
>
> Ran into the same issue when going to 3.5. Completely killed our cluster.
> Only way was to restore a backup.
Hi,
Ran into the same issue when going to 3.5. Completely killed our cluster. Only
way was to restore a backup.
/Oskar
> On 2 aug. 2016, at 07:54, Julien Anguenot wrote:
>
> Hey Jesse,
>
> You might wanna check and comment against that issue:
>
> https://issues.apache.org/jira/browse/CAS
Hey Jesse,
You might wanna check and comment against that issue:
https://issues.apache.org/jira/browse/CASSANDRA-11887
J.
--
Julien Anguenot (@anguenot)
> On Aug 2, 2016, at 3:16 AM, Jesse Hodges wrote:
>
> Hi, I've got a bit of a conundrum. Recently I upgraded from 2.2.3 to 3.7.0
> (
