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
Start OutbackCDX with desired --index-version option.
curl -XPOST http://localhost:8080/myindex/upgrade to start the upgrade.
The server will periodically log progress, note that the remaining time/records estimate is extremely inaccurate.
Upgrading may temporarily require double the disk space. If space is tight that maybe could worked around by periodic compacting at the expense of processing time.
If the upgrade is interrupted by a server restart it's safe to start the upgrade again. It'll scan through the records from the beginning and then continue where it left off.
Downgrading should also work as long as the index doesn't contain any records with extra JSON fields. Hasn't been test though.
The index should still be usable while it has a mix of record versions but there may be corner cases issues around deleting or replacing existing records. Inserting new records during the upgrade should be OK.
The text was updated successfully, but these errors were encountered:
Currently the upgrade process looks like:
--index-version
option.curl -XPOST http://localhost:8080/myindex/upgrade
to start the upgrade.Upgrading may temporarily require double the disk space. If space is tight that maybe could worked around by periodic compacting at the expense of processing time.
If the upgrade is interrupted by a server restart it's safe to start the upgrade again. It'll scan through the records from the beginning and then continue where it left off.
Downgrading should also work as long as the index doesn't contain any records with extra JSON fields. Hasn't been test though.
The index should still be usable while it has a mix of record versions but there may be corner cases issues around deleting or replacing existing records. Inserting new records during the upgrade should be OK.
The text was updated successfully, but these errors were encountered: