[jira] [Commented] (SOLR-10209) UI: Convert all Collections api calls to async requests, add new features/buttons

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-10209) UI: Convert all Collections api calls to async requests, add new features/buttons

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614832#comment-16614832 ]

Amrit Sarkar commented on SOLR-10209:
-------------------------------------

Hi [~janhoy] , thank you for noticing this Jira and improvement. I agree it would be nice to have a simple synchronous option for Backup & Restore.

Unfortunately, I lost track of what I was doing a year ago but can definitely work on this somewhere after mid-October (Activate'18). Else happy and comfortable with fellow contributors and committers taking it forward.

> UI: Convert all Collections api calls to async requests, add new features/buttons
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-10209
>                 URL: https://issues.apache.org/jira/browse/SOLR-10209
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public)
>          Components: Admin UI
>            Reporter: Amrit Sarkar
>            Priority: Major
>         Attachments: SOLR-10209-v1.patch, SOLR-10209.patch, SOLR-10209.patch, SOLR-10209.patch
>
>
> We are having discussion on multiple jiras for requests for Collections apis from UI and how to improve them:
> -SOLR-9818: Solr admin UI rapidly retries any request(s) if it loses connection with the server-
> -SOLR-10146: Admin UI: Button to delete a shard-
> SOLR-10201: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
> Proposal =>
> *Phase 1:*
> Convert all Collections api calls to async requests and utilise REQUESTSTATUS to fetch the information. There will be performance hit, but the requests will be safe and sound. A progress bar will be added for request status.
> {noformat}
> > submit the async request
> if (the initial call failed or there was no status to be found)
> { report an error and suggest the user look check their system before resubmitting the request. Bail out in this case, no retries, no attempt to drive on. }
> else
> { put up a progress indicator while periodically checking the status, Continue spinning until we can report the final status. }
> {noformat}
> *Phase 2:*
> Add new buttons/features to collections.html
> a) "Split" shard
> -b) "Delete" shard-
> c) "Backup" collection
> d) "Restore" collection
> Open to suggestions and feedbacks on this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]