You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by GitBox <gi...@apache.org> on 2022/07/12 13:28:20 UTC
[GitHub] [rocketmq-schema-registry] MatrixHB opened a new issue, #3: Optimize the cache refresh mechanism
MatrixHB opened a new issue, #3:
URL: https://github.com/apache/rocketmq-schema-registry/issues/3
Schema registry uses RocksDB as local cache and uses RocketMQ as remote storage. Now the local cache refresh is implemented by pushConsumer consuming messages from RocketMQ. I found two problems with current code.
1、Using pushConsumer in cluster mode, it must be ensured that each node is a different consumer group, otherwise each node cannot synchronize the complete data.
2、Lack of replay mechanism. When a registry node restart with incomplete local cache, or cold start with empty local cache, we need to pull the complete data from RocketMQ storage to recover the local cache. Therefore, it's better to maintain checkpoint and use pullConsumer to seek specified offset, which is also the suggested way to consume compact topic messages.
--
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: dev-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-schema-registry] ferrirW commented on issue #3: Optimize the cache refresh mechanism
Posted by GitBox <gi...@apache.org>.
ferrirW commented on issue #3:
URL: https://github.com/apache/rocketmq-schema-registry/issues/3#issuecomment-1189019908
There is no good way to solve the second problem right now. Unless RocketMQ COMPACTION Topic can provides semantics like KV.
And i think the first problem also exists in pull mode, we can use ip / hostname / nodeId to ensure that the consumer group is unique.
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [rocketmq-schema-registry] MatrixHB closed issue #3: Optimize the cache refresh mechanism
Posted by GitBox <gi...@apache.org>.
MatrixHB closed issue #3: Optimize the cache refresh mechanism
URL: https://github.com/apache/rocketmq-schema-registry/issues/3
--
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: dev-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org