Readiness & liveness probes #563
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Readiness probe implemented and tested.
Healthines WIP.
…ent-not-working' into 550-provide-health-check-for-docker-image # Conflicts: # docker/Dockerfile # evita_external_api/evita_external_api_system/src/main/java/io/evitadb/externalApi/system/SystemProviderRegistrar.java
Liveness done, but not manually tested.
Enable agent in entry point.
Full implementation manually tested.
Added documentation.
…r-image # Conflicts: # evita_engine/src/main/java/io/evitadb/core/SessionRegistry.java
…ocker-image 550 provide health check for docker image
Bumps [org.bouncycastle:bcprov-jdk18on](https://github.com/bcgit/bc-java) from 1.77 to 1.78. - [Changelog](https://github.com/bcgit/bc-java/blob/main/docs/releasenotes.html) - [Commits](https://github.com/bcgit/bc-java/commits) --- updated-dependencies: - dependency-name: org.bouncycastle:bcprov-jdk18on dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
…tle-bcprov-jdk18on-1.78 build(deps): bump org.bouncycastle:bcprov-jdk18on from 1.77 to 1.78
Added link between readiness and liveness probe. Allow to configure system API port and start delay in Dockerfile using environment variables.
Signed-off-by: Jan Novotný <novotnaci@gmail.com>
Signed-off-by: Jan Novotný <novotnaci@gmail.com>
Fixed work with service loader and probe instantiation.
According to heapdump - current way of switching catalog reference is not safe and there are references to old catalogs trapped in "catalogAccessor" lambda in entity collection. These changes aim to clarify the process of transitioning from one catalog version to another and avoiding the reference leak. According to heapdump - current way of switching catalog reference is not safe and there are references to old catalogs trapped in "catalogAccessor" lambda in entity collection. These changes aim to clarify the process of transitioning from one catalog version to another and avoiding the reference leak.
…uring-transaction-handling
…tion-handling fix(#557): memory leak during transaction handling
When the entity is fetched from the data store, it's entity body storage part is always fetched twice. This becomes a problem when a large number of entities are fetched from the data store, and when the OS file cache is cold, it can mean twice the latency. This fetching is not entirely necessary if we refactor the `enrichEntity` method into two separate ones and call the second one only conditionally.
perf(#559): Entity fetching optimization
We need to write better fuzzy tests that would allow us to exterminate the edge cases in the ChainIndex. It seems that the real production systems may behave sometimes chaotically till they return back to consistent state.
…terexceptions-in-chainindex fix(#531): Random errors and NullPointerExceptions in ChainIndex
…ange data type
If the client uses `attributeGreaterThan("validity", OffsetDateTime.now())`, the exception of a different type will be thrown. He/she needs to update the constraint to `attributeGreaterThan("validity", DateTimeRange.since(OffsetDateTime.now()))` or `attributeGreaterThan("validity", DateTimeRange.between(OffsetDateTime.now(), OffsetDateTime.now()))`, both of which work fine, but this approach is counterintuitive. We should handle the passing of OffsetDateTime and automatically convert it to a time (i.e. the `between` variant) internally to avoid confusion for developers.
…offsetdatetime-against-datetimerange-data-type fix(#556): Add support for comparing OffsetDateTime against DateTimeR…
Fixes revealed by documentation tests. Entities used wrong predicates when prefetched.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.