Bump hazelcast from 3.6-EA to 3.12.13 in /hazelcast-vm-cluster

[dependabot]

Bumps hazelcast from 3.6-EA to 3.12.13.

Release notes

Sourced from hazelcast's releases.

3.12.13 release

v3.12.12

3.12.12 release

v3.12.11

3.12.11 release

v3.12.10

3.12.10 release

3.12.9

This document includes the new features, enhancements and fixed issues for Hazelcast IMDG v3.12.9, Open Source edition release.

Enhancements

• Updated the hazelcast-kubernetes dependency version to 1.5.4. #17256

• Added support for tenant control when creating caches. #17121

Fixes

• Fixed a race issue when creating a cache (JCache) using multiple methods with the same cache name but having different keys. #17284

• Fixed an issue where the repeated calls of executeOnKeys() in Hazelcast clients for NATIVE maps was causing a continuous increase in the used memory and exhaustion of the memory pool after a while. #17271

• Fixed a performance issue when using paging predicates with JDK 8. #17213

• Fixed an issue where ReliableTopicMessageListener was firing a warning when the client is shutting down. #17070

• Fixed an issue where the client-side HazelcastInstance was not throwing a configuration exception when there is a conflict between the dynamic and static configurations. #16927

Contributors

We would like to thank the contributors from our open source community who worked on this release:

• lprimak

3.12.8

This document includes the new features, enhancements and fixed issues for Hazelcast IMDG v3.12.8, Open Source edition release.

Enhancements

• Introduced WAN throttling mechanism: this prevents the WAN consumers from getting overloaded by the WAN producers if transferring the WAN events takes less time than processing them in the target cluster. This can be the case with WAN synchronization if the network latency is low enough. It can be configured using the following properties:

  • hazelcast.wan.consumer.invocation.threshold

  • hazelcast.wan.consumer.ack.delay.backoff.init

  • hazelcast.wan.consumer.ack.delay.backoff.max

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.