Skip to content

Remote compression scheme default to deflate#76580

Merged
Tim-Brooks merged 5 commits intoelastic:7.xfrom
Tim-Brooks:default_to_deflate
Aug 16, 2021
Merged

Remote compression scheme default to deflate#76580
Tim-Brooks merged 5 commits intoelastic:7.xfrom
Tim-Brooks:default_to_deflate

Conversation

@Tim-Brooks
Copy link
Copy Markdown
Contributor

@Tim-Brooks Tim-Brooks commented Aug 16, 2021

Currently the cluster.remote.*.transport.compression_scheme setting
defaults to the transport.compression_scheme value. This commit
modifies this to default to deflate (the existing compression scheme
prior to 7.14) when cluster.remote.*.transport.compress is explicitly set.
This will ensure that users do not accidentally change their compression
scheme for 7.x.

Currently the cluster.remote.*.transport.compression_scheme setting
defaults to the `transport.compression_scheme` value. This commit
modifies this to default to deflate (the existing compression scheme)
prior to 7.14. This will ensure that users do not accidentally change
their compression scheme for 7.x.
@Tim-Brooks Tim-Brooks added >non-issue :Distributed/Network Http and internode communication implementations v7.15.0 labels Aug 16, 2021
@elasticmachine elasticmachine added the Team:Distributed Meta label for distributed team. label Aug 16, 2021
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

Copy link
Copy Markdown
Contributor

@henningandersen henningandersen left a comment

Choose a reason for hiding this comment

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

LGTM.

Comment on lines +87 to +89
explicitBuilder.put(TransportSettings.TRANSPORT_COMPRESSION_SCHEME.getKey(), "lz4");
ConnectionProfile connectionProfile = FakeConnectionStrategy.buildConnectionProfile("cluster-alias", explicitBuilder.build());
assertEquals(Compression.Scheme.DEFLATE, connectionProfile.getCompressionScheme());
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

We may have it elsewhere, but if not, could we add assertions to validate that if REMOTE_CLUSTER_COMPRESSION_SCHEME is set, we use the value set there?

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

Labels

:Distributed/Network Http and internode communication implementations >non-issue Team:Distributed Meta label for distributed team. v7.15.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants