...
Motivation
...
- Remove ineffectiveness from current implementation, avoid any unnecessary but costly operations while still handling each cache entry independently.
- Redesign rebalance process to handle entries in batches.
- Introduce a new mode which will allow to transfer the whole partition file instead of key-value iteration
Risks and Assumptions
// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.
...
// Links to various reference documents, if applicable.
Tickets
...
Jira |
---|
server | ASF JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
maximumIssues | 20 |
---|
jqlQuery | project = Ignite AND labels IN (iep-16) ORDER BY status |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
|
Ways to solve problem on more global level:
- https://issues.apache.org/jira/browse/IGNITE-7935 - a ticket to introduce batch modification;- https://issues.apache.org/jira/browse/IGNITE-8020 - complete redesign of rebalancing process for persistent caches, based on file transfer.