klsince commented on issue #15846: URL: https://github.com/apache/pinot/issues/15846#issuecomment-2945714345
Another approach can be using `seqId` to break the tie, as the seqId field is encoded in LLCSegment and UploadedSegment names so we can save those ZK accesses. When merging segments, we can take `max(seqIds of input segments)` and encode it in the new segment's name via the UploadedSegment name pattern. If the segment name doesn't follow the known pattern, then we fall back on using segment creation time. IIUC, the only inconsistency is from that different servers can have create their own `creation.meta` file kept in their local segment folders. Then only consuming segments are subject to this inconsistency issue, not those uploaded segments. If so, even if an uploaded segment doesn't have known naming pattern, the replicas on different servers would still have same creation.meta value so falling back on creation time would be fine. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
