Skip to content
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

raft entry is too large, region 2, entry size 12014018 #369

Open
bxq2011hust opened this issue Sep 7, 2022 · 1 comment
Open

raft entry is too large, region 2, entry size 12014018 #369

bxq2011hust opened this issue Sep 7, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@bxq2011hust
Copy link

Write ut in rust client, put 10240 kv pairs in one txn, the value is random bytes and length is 10240, the key is format!("key_________________________{}", j) which j is index in 0..10240, commit the txn failed. the error message is

Error: RegionError(Error { message: "raft entry is too large, region 2, entry size 12014018", not_leader: None, region_not_found: None, key_not_in_region: None, epoch_not_match: None, server_is_busy: None, stale_command: None, store_not_match: None, raft_entry_too_large: Some(RaftEntryTooLarge { region_id: 2, entry_size: 12014018 }), max_timestamp_not_synced: None, read_index_not_ready: None, proposal_in_merging_mode: None, data_is_not_ready: None, region_not_initialized: None, disk_full: None })

I run the same ut in c-client, it works fine, I guess the reason is rust client does not split kv pairs into batches in the same region?

@ekexium
Copy link
Collaborator

ekexium commented Sep 7, 2022

I run the same ut in c-client, it works fine, I guess the reason is rust client does not split kv pairs into batches in the same region?

Yes. It should be improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants