gosonzhang commented on issue #6535: URL: https://github.com/apache/inlong/issues/6535#issuecomment-1314705740
It should be caused by too much duplicate data in the offset records of the storage consumption group: in order to make the records more readable[1], for example, each partition consumption record contains the consumption group name, and each partition repeatedly records the maximum and minimum offsets, as a result, the total data record is bloated too much. Considering the traversal of the text display, I plan to still use the text to represent the saved historical offset, but perform field key abbreviation and deduplication processing to reduce the length of the total record. 1. https://github.com/apache/inlong/blob/master/inlong-tubemq/tubemq-server/src/main/java/org/apache/inlong/tubemq/server/broker/offset/OffsetRecordInfo.java#L68  -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
