This message was deleted.
# k3s-contributora
adamant-kite-43734
11/13/2023, 1:43 PMThis message was deleted.
c
creamy-pencil-82913
11/13/2023, 10:31 PMNo, you cannot disable it. Why would you want to? The resource IDs must be strictly sequential in order for nodes to ensure that they are not missing any events. If you see a lot of these being created, it suggests that you’re using a database engine that does not use a strictly sequential auto-increment primary key. This is a core requirement of kine.
e
echoing-spring-73820
11/13/2023, 10:32 PMThanks for explaining
echoing-spring-73820
11/13/2023, 10:32 PMWould it not be enough to require that the sequence is increasing?
echoing-spring-73820
11/13/2023, 10:33 PMI still don't understand why it has to fill the gaps
echoing-spring-73820
11/13/2023, 10:34 PMAs for why I want it: I am trying to bend kine to use postgresql active-active replication
c
creamy-pencil-82913
11/13/2023, 10:53 PMit has to be monotonically increasing. Otherwise there is no way to tell the difference between a missed (dropped) event and a skipped key sequence.
creamy-pencil-82913
11/13/2023, 10:54 PMit would be very bad if the datastore just silently missed changes to resources, the only way it can be sure that it hasn’t missed any is if there is a strict sequence with no skips
creamy-pencil-82913
11/13/2023, 10:55 PManything that uses sharding or skipping of the auto-increment PK will not work with kine
e
echoing-spring-73820
11/13/2023, 11:00 PMOK. That I understand\. I created a sequence which increases in gaps of 2. e.g. 1,3,5 ... etc.
I will have to think of another approach