[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888072#comment-15888072 ] Amrit Sarkar commented on SOLR-10201: - [~cztomek] Yes! We can link the issue to SOLR-10209 instead. We are tracking all the developments on that jira. > 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, SOLR-10201.patch > > > "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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888062#comment-15888062 ] Tomasz Czarnecki commented on SOLR-10201: - [~sarkaramr...@gmail.com] Will this cover SOLR-10211 cases? Should it be connected here. > 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, SOLR-10201.patch > > > "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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15886112#comment-15886112 ] Amrit Sarkar commented on SOLR-10201: - Created new jira: SOLR-10209 to track the developments, suggestions and feedbacks. Thank you. > 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, SOLR-10201.patch > > > "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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883168#comment-15883168 ] Amrit Sarkar commented on SOLR-10201: - [~erickerickson] [~upayavira] for async calls we already have this option: https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-AsynchronousCalls, One new parameter to the heavyweight apis and we can fetch 'check status' content from zk too. I will give it a shot, incorporate async=true for both AddCollection and SplitShard http requests and try to incorporate a small dialog box displaying their status. Thanks. > 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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883133#comment-15883133 ] Upayavira commented on SOLR-10201: -- [~sarkaramr...@gmail.com] look at places where the doNotIntercept is set, and do the same. It seems it is set in the services, in services.js, so you could set it for certain tasks. [~erickerickson] JS is inherently async anyway so you could have a "request submitted" and a "request complete" feedback without any substantial change in the code. To add a 'check status' button would require the backend calls to be async, which would be considerably more work, if they aren't async already. > 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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[
https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882965#comment-15882965
]
Upayavira commented on SOLR-10201:
--
The timeout is set for all components. See js/angular/app.js. see
.factory('httpInterceptor'). That's where the timeout is set.
Also note, in that same method, doNotIntercept. This is an example of how an
caller can signal a specific behaviour to the interceptor. So, you could have a
doNotTimeout option that simply avoids setting the "connectionStatusInactive"
timeout.
> 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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[
https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882909#comment-15882909
]
Amrit Sarkar commented on SOLR-10201:
-
[~upayavira], thank you for the clarification.
I understood that point, I was trying to add a button for SPLITSHARD and was
running into "connection loss" every time I press the button. This is a piece
of code here;
{noformat}
$scope.deleteReplica = function(replica) {
Collections.deleteReplica({collection: replica.collection,
shard:replica.shard, replica:replica.name}, function(data) {
replica.deleted = true;
$timeout(function() {
$scope.refresh();
}, 2000);
});
}
{noformat}
After 2000ms, refresh the page. I went deeper into dev-console on Chrome, was
not able to find where we are setting out timeout? or 2sec is the timeout? or
it has nothing to do with the JS call and timeouts are API specific?
> 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
[jira] [Commented] (SOLR-10201) Admin UI: Add Collection "creates collection", "Connection to Solr lost", when replicationFactor>1
[ https://issues.apache.org/jira/browse/SOLR-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15882667#comment-15882667 ] Upayavira commented on SOLR-10201: -- This is generally due to the timeout. If a request takes longer than the timeout, it is assumed to imply that the server is down, which for long running requests isn't necessarily the case. It would be great to add an option for certain HTTP requests to say "this may take a long time, don't set a timeout as you would normally". > 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
