You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In DataHub version 0.14.0.2, when running a restore indices job, the job successfully restores 100% of the indices. However, instead of terminating after completing the restore, the job continues searching for more indices and ends up failing with an error when no more indices are available to restore.
To Reproduce
1. Go to DataHub and initiate a restore indices job.
2. Monitor the job progress through logs.
3. After reaching 100% restoration, observe that the job continues searching for indices.
4. The job fails with an error: Failed Step 4/4: SendMAEStep. Failed after 0 retries. Exiting upgrade RestoreIndices with result FAILED. Exiting...
Expected behavior
Once the job reaches 100% completion (i.e., all indices have been restored), it should terminate gracefully without searching for additional indices and without throwing an error.
Screenshots
Desktop (please complete the following information):
OS: [Linux
Browser [e.g. chrome, safari]
Version [e.g. 22]
Additional context
There may be a missing check for job completion after 100%, or an incorrect termination condition.
The text was updated successfully, but these errors were encountered:
Describe the bug
In DataHub version 0.14.0.2, when running a restore indices job, the job successfully restores 100% of the indices. However, instead of terminating after completing the restore, the job continues searching for more indices and ends up failing with an error when no more indices are available to restore.
To Reproduce
1. Go to DataHub and initiate a restore indices job.
2. Monitor the job progress through logs.
3. After reaching 100% restoration, observe that the job continues searching for indices.
4. The job fails with an error: Failed Step 4/4: SendMAEStep. Failed after 0 retries. Exiting upgrade RestoreIndices with result FAILED. Exiting...
Expected behavior
Once the job reaches 100% completion (i.e., all indices have been restored), it should terminate gracefully without searching for additional indices and without throwing an error.
Screenshots

Desktop (please complete the following information):
Additional context
There may be a missing check for job completion after 100%, or an incorrect termination condition.
The text was updated successfully, but these errors were encountered: