| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Client-specific binding: Bound to a dedicated client, with no cross-gateway sharing allowed. Once you decide to serve 1 or more domains on a listing-cache enabled gateway it must serve all requests to those domain(s) exclusively. This is achieved by configuring your load-balancer with dedicated host-based traffic redirection rules.
Non-persistent cache: The disk/memory cache is discarded by default on restart.
Limited lifecycle and recursivedeletion support: No support for bucket lifecycle policies, delete lifepoints, or recursive deletes. All writes and deletes must originate from the gateway.
Memory constraints: Caching large volumes of data can quickly consume system memory. Misconfiguring cache sizes can lead to memory exhaustion or excessive eviction, reducing cache effectiveness.
Delimiters support: Custom delimiters are not yet supported, only forward slash "/".
Replication support: <pending engineering feedback>, do Do not setup replication when LC is enabled.
Not supported functionalities: Custom delimiters, S3 lifecycles, and recursive deletes.
...
Perform basic functionality tests:
Verify data retrieval and storage through LC.
Test operations within pseudo folders.
Check system logs for any errors or warnings.
Monitor performance metrics to ensure the hardware is sufficient.
Step 5: Go Live
...