Post update to 1.0.1.1 - indexing lost!
We updated from 1.0.1 to 1.0.1.1 overnight. Queries that previously returned a multitude of work items are now only returning those created or updated since the server update. It appears that we lost the index on the existing work items. Things are being indexed as they are created or edited.
Is there a way to force reindexing? This is a huge problem. The server update was done about 6 hours ago.
Is there a way to force reindexing? This is a huge problem. The server update was done about 6 hours ago.
3 answers
We updated from 1.0.1 to 1.0.1.1 overnight. Queries that previously
returned a multitude of work items are now only returning those
created or updated since the server update. It appears that we lost
the index on the existing work items. Things are being indexed as
they are created or edited.
Is there a way to force reindexing? This is a huge problem. The
server update was done about 6 hours ago.
The full text index is held separately from the repository. I assume this
location is now different after the upgrade? You should see its location
in the server log in the startup part or in teamserver.properties. But as
you have already created new work items, those would be missing if you
copied the existing index to the new location.
Repotools has an option to re-create the full text index:
-rebuildTextIndices
--
Regards,
Patrick
Jazz Work Item Team
It should not take more than 20 min to rebuild the text indices for 7000 work items.
--- Balaji
--- Balaji
Thanks. Not knowing how long it will take to rebuild the indices we have scheduled it for off-hours. Our repository isn't big yet (<7,000 work items) and backed by DB2 but we were concerned that the downtime would be too much for a middle of the work day re-indexing.