How can I start rm/rdng while the reindex is running?
We needed to re-index our rdng 5.0.2 repository. For us, the triple-live indexes take about 10 hours. In the past the triple history indexes used to take about 10 minutes. Now our triple history is estimating 5 days to complete and has progressed .1% in about an hour.
We have had the re-index job crash with Out of Memory errors and have been able to have the jvm start the indexing service to "finish" indexing.
Has anyone has any success with killing (kill -6) the re-index job so the jvm can be re-started for users? They are not going to happy with the app down for another 5 days.
|
2 answers
I think you should work this as a support case ASAP. |
Thanks for your quick response. We do have a case open which lead to the re-index.
Trying to see what the practitioners have done around this or IBM to step in and say that is "safe."
Thanks!
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.