-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Comparing changes
Open a pull request
base repository: hazelcast/hazelcast
base: v5.3.6
head repository: hazelcast/hazelcast
compare: v5.3.7
- 11 commits
- 62 files changed
- 8 contributors
Commits on Mar 26, 2024
-
Add copybara workflows [5.3.7]
GitOrigin-RevId: acb4b5aa6410b0200b60156370f821163285166f
Configuration menu - View commit details
-
Copy full SHA for dc73506 - Browse repository at this point
Copy the full SHA dc73506View commit details -
Disable dependabot in EE (#393) [5.3.7]
Disable dependabot in EE (cherry picked from commit 4afbfb3003a2bec9f8d77d9081be281d513907f8) GitOrigin-RevId: 3847de4445c41e105c7b13d776a5965765293fec
Configuration menu - View commit details
-
Copy full SHA for 0539187 - Browse repository at this point
Copy the full SHA 0539187View commit details -
Update POM version to 5.3.7-SNAPSHOT [HZ-4188][5.3.7] (#1197)
Preparing 5.3.7 release branch created manually from v5.3.6 tag Fixes: [HZ-4188] GitOrigin-RevId: f58dfe6af086c69057cb393ff60714d0a494ed98
Configuration menu - View commit details
-
Copy full SHA for 39798a5 - Browse repository at this point
Copy the full SHA 39798a5View commit details
Commits on Mar 27, 2024
-
Batch partition replica updates [HZ-3652] [5.3.7] (#1201)
Since Hazelcast IMDG 4.1 with the introduction of parallel migrations, the "partition assignments version", a monotonically increasing version number for the whole partition replica assignments data structure, was replaced with a "partition state stamp" - a hash calculated over individual partitions' version. On each partition replica assignment update, the partition state stamp needs to be recalculated. In certain cases, it is expected that all partition replica assignments will be updated: - during initial partitions assignment ("first arrangement") - when a member that joins the cluster applies the partition replica assignments, as received from master member - when a member recovers partition replica assignments from persistence In such cases, updating the partition state stamp on each partition replica update is inefficient. Instead, the partition state stamp can be updated just once, after the whole batch of partition replica assignments has been applied. Measured the following timings: - Initial partitions assignment on a single member with 20K partitions - current `master` branch: 3870 millis (20001 partition stamp updates) - with this PR: 28 millis (1 partition stamp update) - Apply initial partition state on the 3rd member joining a cluster with 2 members - current `master` branch: 3260 (40002 partition stamp updates) - with this PR: 4 millis (1 partition stamp update) (cherry picked from commit 1030206 with an additional change to adapt test for JUnit 4 that is in use in 5.3 series) Fixes [HZ-3652] on 5.3.7 branch Backport of #25905 [HZ-3652]: https://hazelcast.atlassian.net/browse/HZ-3652?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ GitOrigin-RevId: 26505d9bab59a4dcf1a4a7a8ed36bac661e43b39Configuration menu - View commit details
-
Copy full SHA for fecc523 - Browse repository at this point
Copy the full SHA fecc523View commit details -
Bump
grpcto mitigate CVE-2023-44487 [5.3.7][HZ-4299] (#1207)Fixes #25809 / [HZ-4299](https://hazelcast.atlassian.net/browse/HZ-4299) Backport of https://github.com/hazelcast/hazelcast-mono/pull/97 [HZ-4299]: https://hazelcast.atlassian.net/browse/HZ-4299?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [HZ-4299]: https://hazelcast.atlassian.net/browse/HZ-4299?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ [HZ-4299]: https://hazelcast.atlassian.net/browse/HZ-4299?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ GitOrigin-RevId: 17a550254d2d76a8e80ea823789c0efcffb29043
Configuration menu - View commit details
-
Copy full SHA for bbbbcf8 - Browse repository at this point
Copy the full SHA bbbbcf8View commit details -
Configuration menu - View commit details
-
Copy full SHA for 07040be - Browse repository at this point
Copy the full SHA 07040beView commit details -
Fix Vulnerability in PostgreSQL driver for CVE-2024-1597 [HZ-4631] [5…
….3.7] (#1211) GitOrigin-RevId: 20919143b4352bfa82ba6840ce4c443223e18f93
Configuration menu - View commit details
-
Copy full SHA for e7f3c9b - Browse repository at this point
Copy the full SHA e7f3c9bView commit details -
Update aws-java-sdk-bundle version to 1.12.688 [HZ-4631] (#1209)
GitOrigin-RevId: 8879bbb6efe07049b340e6ec6ebb13f6c0640daa
Configuration menu - View commit details
-
Copy full SHA for fdf59c3 - Browse repository at this point
Copy the full SHA fdf59c3View commit details
Commits on Mar 28, 2024
-
Fix Vulnerability in elasticsearch 7.17.13 CVE [HZ-4631] [5.3.7] (#1206)
GitOrigin-RevId: 371536ef7c34b840dc91b091142a47313e2f88de
Configuration menu - View commit details
-
Copy full SHA for e077a22 - Browse repository at this point
Copy the full SHA e077a22View commit details -
Add RN for Platform OS 5.3.7 (#1236)
GitOrigin-RevId: 7ac28f1d733c8c25ad50155173ea5d25e73589f3
Configuration menu - View commit details
-
Copy full SHA for 3b01aeb - Browse repository at this point
Copy the full SHA 3b01aebView commit details
Commits on Apr 3, 2024
-
GitOrigin-RevId: 4dfe7f81d37946b51928742c52ac5e5d9c15e80f
Configuration menu - View commit details
-
Copy full SHA for e2dadf5 - Browse repository at this point
Copy the full SHA e2dadf5View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v5.3.6...v5.3.7