[
https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883020#comment-15883020
]
Amrit Sarkar commented on SOLR-10201:
-------------------------------------
Got it, thanks!
HTTP requests take more/long time when there are more than one node is involved
in heavy action (create directories, copying configs to ZK, copy data over
nodes). *AddCollection* and *SplitShard* are definitely the two of them. Should
we set _doNotTimeout_ for _AddCollection_, and give the user a boolean option
for the same? or we set it at our end, in the JS api call?
> 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
