dCache / nfs4j

Pure Java NFSv3 and NFSv4.2 implementation
Other
240 stars 76 forks source link

build(deps): bump hazelcast from 4.1.8 to 4.1.10 #117

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps hazelcast from 4.1.8 to 4.1.10.

Release notes

Sourced from hazelcast's releases.

v4.1.10

This document lists the new features, enhancements, fixed issues and, removed or deprecated features for Hazelcast IMDG 4.1.z releases. The numbers in the square brackets refer to the issues in Hazelcast's GitHub repositories.

==== 4.1.10 ====

Enhancements

  • Improved connection handling. #21644
  • To decrease the load on the Management Center for large clusters, the level of network related metrics has been changed to DEBUG. When you need these metrics, you can use the hazelcast.metrics.debug.enabled property. #21260

Fixes

  • Fixed an issue where replication over WAN was failing on the source cluster members, when there are multiple batch publishers configured in a single WAN replication. #22498
  • Fixed an issue where the cluster was failing to operate since the indexes on backup partitions were removed by map.ClearBackupOperation. #22305
  • Fixed an issue where a cluster could not be formed when security is enabled, various client permissions are set, and multiple members are started simultaneously. #21507

==== 4.1.9 ====

Enhancements

Fixes

  • Fixed an issue where a cluster was unresponsive when you perform a health check to see the members are in the safe state; cluster members were hanging in the REPLICA_NOT_SYNC state during such health checks. #21205
  • Fixed an issue where the list of members in the cluster was reset to an empty list when member IDs change after a cluster restart: this was causing startup failures since Hazelcast could not manage the events due to the empty member list after a restart. #21181
  • Fixed an issue where the statistics like puts and removals were not increasing when these operations are executed through Transactional interface. #21100
  • Fixed an issue where Hazelcast clients, which have only the IP address of a member to connect (but the member also has a hostname), were not able to connect to the cluster. #20632

==== 4.1.8 ====

  • For the distributions packages of IMDG, we updated the vulnerable version of log4j2 in Management Center to 2.17.0. No changes were made to the IMDG code.

==== 4.1.7 ====

  • For the distributions packages of IMDG, we updated the vulnerable version of log4j2 in Management Center to 2.15.0. No changes were made to the IMDG code.

==== 4.1.6 ====

Enhancements

  • Improved the log message that is displayed when using the hazelcast.io.selectorMode property to decrease the high CPU usage. The previous misleading message read as "Recreated Selector because of possible java/network stack bug". It has been changed to "Selector was rebuilt, consider updating Java and/or your network stack drivers". #19761
  • Introduced the hazelcast.internal.map.expired.key.scan.timeout.nanos property to limit the execution time of the cleanup operations, i.e., entry expiration tasks of a map; this is to prevent the increased CPU usage as the partition size grows. #19663

Fixes

  • Hazelcast was executing cluster wide operations when you query the state of a member using the health check endpoint - it was causing to kill all the members in a cluster; this issue has been fixed. #19837
  • The increment command (incr) in the Memcache client was returning the ASCII code of the expected result; this interpretation issue has been fixed. #19681

==== 4.1.5 ====

... (truncated)

Commits
  • c2b1293 Upgrade version to 4.1.10
  • 9555e6f Prepare release 4.1.10
  • 66cfca2 Adding OS 4.1.10 release notes along with that of all 4.1.z series. (#22823)
  • 4847c2e Handle null values of AddMapConfigMessageTask's nullable fields (#22821)
  • 3c1b70e Convert HotRestartTriggerBackupMessageTask and ShutdownClusterMessageTask to ...
  • 11aace9 Upgrade jackson to 2.14.0 [4.1.z] (#22393)
  • 767ef01 Fixed ClearBackupOperation [HZ-1210], BACKPORT (#22305)
  • 2672dc7 Queue priority test fix [HZ-1096] (#21268)
  • 9685c0f Fix non-finalized items in wan queue [HZ-1502] [4.1.z] (#22437) (#22498)
  • c1e9ae5 Fix Throwable.initCause when exception already has cause [4.1.z] API-1387 (#2...
  • Additional commits viewable in compare view


Dependabot compatibility score

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](https://github.com/dCache/nfs4j/network/alerts).