Comments (4)
lukashornych
commented on July 3, 2024
Doesn't this solve the alive endpoints we provide in GQL and REST endpoint? Should this do something more?
from evitadb.
novoj
commented on July 3, 2024
Yes, I'm implementing it on the "system" endpoint so we don't have to rely on APIs that could be disabled at any time. I will also detect the situations when queues are full and requests are rejected, also when GC cannot free memory and the system will crash due to insufficient memory, and also when there are a lot of internal errors that might signal some problem. This is not covered by our "liveness" probes in the GQL / REST APIs.
from evitadb.
novoj
commented on July 3, 2024
We should also prepare readiness probe. See Kubernetes documentation
from evitadb.
novoj
commented on July 3, 2024
Documented here: https://evitadb.io/documentation/operate/monitor?lang=evitaql#readiness-and-liveness-probes
from evitadb.
Related Issues (20)
- Issues applying partial rollback in atomic entity mutation
- Ensure the computation is killed quickly when timeout is exceeded HOT 1
- Transaction pipeline finishing with exception
- Histogram values are not monotonic in Inverted histogram
- Support for layering configuration
- Exception when querying non-existent entity by unique attribute HOT 1
- Avoid certificate generation when no TLS endpoint is configured
- Catalog data file gets broken after compaction
- Query targeting localized attribute returns no result
- Referenced entity bodies are not returned for hierarchically fetched parents
- Selecting facet combination from different groups enables hasSense for invalid facets
- Allow custom price for sale parameters for `multiplePricesForSaleAvailable` field in GQL HOT 2
- Filter references without referenced objects (optionally) HOT 1
- Support for disabling keep-alive header in configuration
- Unique ID identifying the catalog
- System status endpoint doesn't work
- SortIndex handles BigDecimal in wrong way
- System services for evitaLab HOT 1
- Failed to remove all references
- Remove classifier token distinction in evitaQL parser HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from evitadb.