Hi, Good Evening. We are seeing below WARNs in controller logs and segment start & end times are negative , what will be the root cause?

2021/04/16 16:59:54.827 WARN [TimeRetentionStrategy] [pool-10-thread-5] REALTIME segment: <>__0__982__20210312T0906Z of table: <>_REALTIME has invalid end time: -9223372036854775808 MILLISECONDS
2021/04/16 16:59:54.827 WARN [TimeRetentionStrategy] [pool-10-thread-5] REALTIME segment: <>__0__983__20210312T0936Z of table: <>_REALTIME has invalid end time: -9223372036854775808 MILLISECONDS
2021/04/16 16:59:54.827 WARN [TimeRetentionStrategy] [pool-10-thread-5] REALTIME segment: <>__0__984__20210312T1006Z of table: <>_REALTIME has invalid end time: -9223372036854775808 MILLISECONDS

Hmm, your segment name seems to be

<>

?

No, I replaced with

<>

sorry for that 🙂

Lol, ok

The segment seems to have been created on March 12. Perhaps the segment has invalid data on time column? Did you by any chance change the schema since then? What is the retention on your table?

retention is 30 days

Long.MIN_VALUE seems to suggest it is null in the incoming stream?

If you have access to the server, you can check the min and max values of the time column in the rows in the segment

Ok, will try that

You will find it in the metadata of the segment, in the director where the segment files are stored. A text file called

metadata.properties

He did and it is Long.MIN_VALUE, suggesting that incoming values are likely null