It is properly restored, we double checked. We worked around the issue by restarting the query server.
But it seems a bad bug. On Tue, Oct 22, 2019, 11:34 AM Thomas D'Silva <twdsi...@gmail.com> wrote: > Are you sure SYSTEM.SEQUENCE was restored properly? What is the current > value of the sequence in the restored table? > > On Fri, Oct 4, 2019 at 1:52 PM jesse <chat2je...@gmail.com> wrote: > >> Let's say there is a running cluster A, with table:books and >> system.sequence current value 5000, cache size 100, incremental is 1, the >> latest book with sequence id:4800 >> >> Now the cluster A snapshot is backed up & restored into cluster b, >> system.sequence and books table are properly restored, when we add a new >> book, the book gets sequence id: 12, why it is not 4801 or 5001? >> >> Our Phoenix version : 4.14.2 >> >> Thanks >> >> >> >>
