Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
- Though there is no issues with SOLR, on Atlas startup Index recovery is getting started as it's considering 1970-01-01T00:00:00Z as default recovery start time.
When no index recovery data is available by default it'll consider recovery start time based on TTL i.e., (current time - tx.log TTL).
By default SOLR tx.log default ttl is configured as 10days.
2. Custom start time configuration atlas.graph.index.recovery.start.time is not working as it conflicts with janusgraph internal configurations. This config should be updated to atlas.index.recovery.start.time
3. When SOLR went down with existing architecture we note down start time with a buffer of solr health checkup frequency which will be (current time - retrytime of solr health). To avoid any possible corner case scenarios updating the buffer two times of retry time so next recovery start time should be (current time - 2 * retry time)
4. Added REST support for index recovery which can give more flexibility to the customer to start index recovery on-demand and will be valubale feature.
a. Get index recovery timing details
API: GET api/atlas/v2/indexrecovery/
Response:
{ "Latest start time": "2023-03-25T20:34:59.704Z", => Start time of recent/upcoming Index recovery "On-demand start time": "2023-03-24T06:17:23.656Z", => Start time of index recovery requested through REST API "Previous start time": "2023-03-25T20:24:51.583Z" => Start time of previous index recovery }
b. Start index recovery at a specific time
API: POST api/atlas/v2/indexrecovery/start?startTime=2023-03-24T06:17:23.656Z
Response:
On success => 200 OK
On empty start Time => 400 Bad request
On Index recovery failure => 500 Internal Server Error
Attachments
Issue Links
- links to
