Skip to content

IGNITE-28687 Remove MarshallableMessage from PartitionUpdateCountersMessage#13140

Open
Vladsz83 wants to merge 2 commits into
apache:masterfrom
Vladsz83:No-Marshallable-for-PartitionUpdateCountersMessage
Open

IGNITE-28687 Remove MarshallableMessage from PartitionUpdateCountersMessage#13140
Vladsz83 wants to merge 2 commits into
apache:masterfrom
Vladsz83:No-Marshallable-for-PartitionUpdateCountersMessage

Conversation

@Vladsz83
Copy link
Copy Markdown
Contributor

No description provided.

@github-actions
Copy link
Copy Markdown

Possible compatibility issues. Please, check rolling upgrade cases

This PR modifies protected classes (with Order annotation).
Changes to these classes can break rolling upgrade compatibility.

Affected files:

  • modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/PartitionUpdateCountersMessage.java

@Vladsz83 Vladsz83 changed the title Remove MarshallableMessage from PartitionUpdateCountersMessage IGNITE-28687 Remove MarshallableMessage from PartitionUpdateCountersMessage May 15, 2026
@sonarqubecloud
Copy link
Copy Markdown


if (data.length < req)
data = Arrays.copyOf(data, data.length << 1);
data = Arrays.copyOf(data, (int)(data.length * 1.33f));
Copy link
Copy Markdown
Contributor

@shishkovilja shishkovilja May 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you trying to eliminate unnecessary allocations?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no quarantine of invoking finishUpdating(). We lack a message finalization life cycle (not prepareMarshall()). If wasn't finished/optimized, less memory would wasted. Also, growing with factor of 1.3 or 1.5 is a common practice too. x2 looks too sweeping.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants