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
When a user first load a Nunaliit page, if the database in indexing, then there is a definite lag before the page is shown. To the end user, it looks like the site is broken.
This happens with CouchDb, since indexing is lazy. It waits until a design document is accessed before it indexes the views in it.
The indexing status and its progress is available from CouchDb. It is located at /_active_tasks This URL is not visible to an end user.
It would be possible for the Nunaliit server to track the _active_tasks URL and report the status to the front end application. This would allow informing the end user that the database is busy and how far along it is.
The text was updated successfully, but these errors were encountered:
I think I'd rather investigate the implications of Issue #625 to eliminate the hang while reindexing before building user-facing code to make them wait.
When a user first load a Nunaliit page, if the database in indexing, then there is a definite lag before the page is shown. To the end user, it looks like the site is broken.
This happens with CouchDb, since indexing is lazy. It waits until a design document is accessed before it indexes the views in it.
The indexing status and its progress is available from CouchDb. It is located at /_active_tasks This URL is not visible to an end user.
It would be possible for the Nunaliit server to track the _active_tasks URL and report the status to the front end application. This would allow informing the end user that the database is busy and how far along it is.
The text was updated successfully, but these errors were encountered: