[
https://issues.apache.org/jira/browse/SOLR-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Sarkar updated SOLR-10209:
--------------------------------
Description:
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.
was:
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.
> 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
> Attachments: SOLR-10209.patch, SOLR-10209.patch, SOLR-10209-v1.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
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
