dang-stripe commented on issue #14067: URL: https://github.com/apache/pinot/issues/14067#issuecomment-2372473553
We've managed to hit this exception in our test clusters on 1.2 as well w/ snapshot + preload. I haven't been able to reproduce it yet though. The segments were in ERROR state. The only relevant logs seem to be these snapshot failures, but I do not see any `Caught exception while taking snapshot` logs from https://github.com/apache/pinot/blob/master/pinot-segment-local/src/main/java/org/apache/pinot/segment/local/upsert/BasePartitionUpsertMetadataManager.java ``` [2024-09-23 15:15:23.682414] INFO [setup_attempts_REALTIME-327710-ConcurrentMapPartitionUpsertMetadataManager] [setup_attempts__327710__147__20240923T1515Z:138928] Taking snapshot for 147 segments [2024-09-23 15:15:23.682430] INFO [ImmutableSegmentImpl] [setup_attempts__327710__147__20240923T1515Z:25] Persisted validDocIds for segment: setup_attempts__327710__146__20240923T1115Z with: 3 valid docs [2024-09-23 15:15:23.682447] WARN [setup_attempts_REALTIME-327710-ConcurrentMapPartitionUpsertMetadataManager] [setup_attempts__327710__147__20240923T1515Z:138928] Missed taking snapshot for 146 immutable segments [2024-09-23 15:15:23.682466] INFO [setup_attempts_REALTIME-327710-ConcurrentMapPartitionUpsertMetadataManager] [setup_attempts__327710__147__20240923T1515Z:138928] Finished taking snapshot for 1 immutable segments with 3 primary keys (out of 147 total segments, 0 are consuming segments) in 1 ms ``` -- 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
