-
Notifications
You must be signed in to change notification settings - Fork 11.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ISSUE #7064] [RIP-66-1] Support KV(RocksDB) Storage for Metadata #7092
[ISSUE #7064] [RIP-66-1] Support KV(RocksDB) Storage for Metadata #7092
Conversation
protected void removeConsumerOffset(String topicAtGroup) { | ||
|
||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When was the method called?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This interface is mainly to let RocksDBConsumeOffsetManager to override and delete the data in rocksdb, you can see the overridden method in RocksDBConsumeOffsetManager.
* See the License for the specific language governing permissions and | ||
* limitations under the License. | ||
*/ | ||
package org.apache.rocketmq.client.consumer.store; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Putting this class in the client module is a bit strange
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because I found OffsetSerializeWrapper under the client moudle, so I put RocksDBOffsetSerializeWrapper in this directory as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OffsetSerializeWrapper is used in client module, RocksDBOffsetSerializeWrapper is used in broker module instead of client module, so I think this is not appropriate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK
@@ -50,7 +50,7 @@ public static void main(String[] args) throws MQClientException { | |||
* </pre> | |||
*/ | |||
// Uncomment the following line while debugging, namesrvAddr should be set to your local address | |||
// consumer.setNamesrvAddr(DEFAULT_NAMESRVADDR); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be better not to modify this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to modify this, please also modify the comments above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK
Signed-off-by: Li Zhanhui <[email protected]>
@fujian-zfj Fixed bazel build scripts for you |
OK,thank you |
Signed-off-by: Li Zhanhui <[email protected]>
…etmq into develop_rocksdb_metadata
Which Issue(s) This PR Fixes
Fixes #7064
Brief Description
This proposal mainly optimizes and solves the existing perfermance problems in the million-topic scenario :