hanahmily opened a new issue, #11494:
URL: https://github.com/apache/skywalking/issues/11494
### Search before asking
- [X] I had searched in the
[issues](https://github.com/apache/skywalking/issues?q=is%3Aissue) and found no
similar feature requirement.
### Description
## Background
Currently, BanyanDB does not have a mechanism to handle the expiration of
data in the `SeriesDatabase`. This lack of a GC mechanism can lead to
inefficient use of resources, particularly in scenarios where there is a sudden
switch in the SeriesDatabase. This sudden switch can cause CPU spikes, which
can potentially impact the performance of the system.
## Detailed Description
The proposed solution includes the following steps:
1. **TTL Reading:** The GC mechanism should be able to read the TTL setting
for each shard where the SeriesDatabase resides. This value will determine when
the GC process should be initiated.
2. **GC Trigger for New SeriesDatabase Creation:** When each shard reaches
its TTL, the GC process should be triggered. This process includes the creation
of a new SeriesDatabase.
3. **Data Ingestion:** The new SeriesDatabase should start accepting the
data linearly over the next two hours. This procedure ensures a smoother
transition and avoids a sudden influx of data to the new database.
4. **Switching Mechanism:** Once the TTL of the old shard is reached and the
GC process is completed, the system should seamlessly switch to the new
SeriesDatabase.
### Use case
_No response_
### Related issues
_No response_
### Are you willing to submit a pull request to implement this on your own?
- [ ] Yes I am willing to submit a pull request on my own!
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://www.apache.org/foundation/policies/conduct)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
notifications-unsubscr...@skywalking.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
