Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display progress on database indexing #722

Open
jpfiset opened this issue Feb 27, 2018 · 1 comment
Open

Display progress on database indexing #722

jpfiset opened this issue Feb 27, 2018 · 1 comment
Labels
Enhancement Desired improvement to design or implementation that adds value.
Milestone

Comments

@jpfiset
Copy link
Collaborator

jpfiset commented Feb 27, 2018

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.

@jpfiset jpfiset added the Enhancement Desired improvement to design or implementation that adds value. label Feb 27, 2018
@jpfiset jpfiset added this to the 2.2.9 milestone Feb 27, 2018
@jpfiset jpfiset self-assigned this Feb 27, 2018
@ahayes
Copy link
Member

ahayes commented Feb 27, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Desired improvement to design or implementation that adds value.
Projects
None yet
Development

No branches or pull requests

2 participants