It seems, that we can compare UUID s and find the biggest or smallest
On Tue, 21 May 2019 at 11:15, Aleksey Korolkov wrote:
> Unfortunately not, I had the same idea, but it is not timeuuid, an example
> from my cluster (5edde338-ce0d-3ead-bbee-63010ffbee6d)
>
> On Tue, 21 May 2019 at 10:40, Rhys
Unfortunately not, I had the same idea, but it is not timeuuid, an example
from my cluster (5edde338-ce0d-3ead-bbee-63010ffbee6d)
On Tue, 21 May 2019 at 10:40, Rhys Campbell
wrote:
> I'd hazzard a guess that the uuid contains a datetime component
>
> Aleksey Korolkov schrieb am Di., 21. Mai 201
I'd hazzard a guess that the uuid contains a datetime component
Aleksey Korolkov schrieb am Di., 21. Mai 2019, 09:36:
> Thanks for the feedback.
> I also think that node choose like "last wins" but I could not find any
> timestamp of schema creation in system tables.
> Hope this is not the order
Thanks for the feedback.
I also think that node choose like "last wins" but I could not find any
timestamp of schema creation in system tables.
Hope this is not the order of an element in Map or List)
On Tue, 21 May 2019 at 02:58, Stefan Miklosovic <
stefan.mikloso...@instaclustr.com> wrote:
> M
My guess is that the "latest" schema would be chosen but I am
definitely interested in in-depth explanation.
On Tue, 21 May 2019 at 00:28, Alexey Korolkov wrote:
>
> Hello team,
> In some circumstances, my cluster was split onto two schema versions
> (half on one version, and rest on another)
> I
Hello team,
In some circumstances, my cluster was split onto two schema versions
(half on one version, and rest on another)
In the process of resolving this issue, I restarted some nodes.
Eventually, nodes migrated to one schema, but it was not clear why they
choose exactly this version of schema?
