[
https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883117#comment-15883117
]
Erick Erickson commented on SOLR-10201:
---------------------------------------
My question is whether heavyweight operations like SPLITSHARD should even _try_
to be synchronous from the UI. Any timeout will be wrong for user N+1.
Would it make more sense to always make it async and provide some sort of
"check status" button? Or even let the user say whether it should be sync or
async with perhaps a timeout _they_ could specify for the op? I mention this
last just for discussion, frankly I'd be fine with not giving them a choice;
firing it async and providing a "check progress" button. It'd be cool if we had
a progress bar, but only if it's easy.
FWIW, mostly random musings.
> Admin UI: Add Collection "creates collection", "Connection to Solr lost",
> when replicationFactor>1
> --------------------------------------------------------------------------------------------------
>
> Key: SOLR-10201
> URL: https://issues.apache.org/jira/browse/SOLR-10201
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: 6.2
> Reporter: Amrit Sarkar
> Attachments: screenshot-1.png
>
>
> "Add Collection" fails miserably when replicationFactor >1.
> There must be a better way to handle the request we are making through JS.
> PF screenshot.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
