Uh oh!
There was an error while loading. Please reload this page.
HBASE-28287 MOB HFiles are expired earlier than their reference data - #5599
Conversation
Apache-HBase
commented
Dec 28, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Dec 28, 2023
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Dec 28, 2023
💔 -1 overall
This message was automatically generated. |
Uh oh!
There was an error while loading. Please reload this page.
Apache9
commented
Jan 4, 2024
I still do not fully understand the problem here... If we do not set millis to zero, it will only affect the life time of a MOB file for less than 1 second, how could it make the MOB file expire 2 hours earlier? |
liuwenjing17
commented
Jan 5, 2024
Because in org.apache.hadoop.hbase.mob.MobUtils, the creation time of mob files is obtained by parsing their names from fileName using the statement (Date fileDate = parseDate(MobFileName.getDateFromName(fileName));). For instance, data created on 20240105, their timestamps will be parsed as 1704384000000 (2024-01-05 00:00:00). In this way, when the master expired mob thread starts, it may affect the life time of a MOB file for less than 1 day. |
Then the problem is we should use a timestamp instead of '20240105' in the mob file name? I still do not understand why setting MILLISECOND to 0 can solve the problem... |
liuwenjing17
commented
Jan 5, 2024
Here is an example:
And here is the link to jira: https://issues.apache.org/jira/browse/HBASE-28287 |
Apache9
commented
Jan 5, 2024
OK. Got it. Thanks for the explaination. |
Apache-HBase
commented
Jan 10, 2024
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 10, 2024
🎊 +1 overall
This message was automatically generated. |
Apache-HBase
commented
Jan 10, 2024
🎊 +1 overall
This message was automatically generated. |
No description provided.