Filed: https://issues.apache.org/jira/browse/SOLR-5945
On Tue, Apr 1, 2014 at 11:10 AM, Jessica Mallet wrote:
> Will do Mark. Thanks!
>
>
> On Sun, Mar 30, 2014 at 1:29 PM, Mark Miller wrote:
>
>> We don't currently retry, but I don't think it would hurt much if we did
>> - at least briefly.
>>
Will do Mark. Thanks!
On Sun, Mar 30, 2014 at 1:29 PM, Mark Miller wrote:
> We don't currently retry, but I don't think it would hurt much if we did -
> at least briefly.
>
> If you want to file a JIRA issue, that would be the best way to get it in
> a future release.
>
> --
> Mark Miller
> abo
We don’t currently retry, but I don’t think it would hurt much if we did - at
least briefly.
If you want to file a JIRA issue, that would be the best way to get it in a
future release.
--
Mark Miller
about.me/markrmiller
On March 28, 2014 at 5:40:47 PM, Michael Della Bitta
(michael.della.bi.
Hi, Jessica,
We've had a similar problem when DNS resolution of our Hadoop task nodes
has failed. They tend to take a dirt nap until you fix the problem
manually. Are you experiencing this in AWS as well?
I'd say the two things to do are to poll the node state via HTTP using a
monitoring tool so
Hi,
First off, I'd like to give a disclaimer that this probably is a very edge
case issue. However, since it happened to us, I would like to get some
advice on how to best handle this failure scenario.
Basically, we had some network issue where we temporarily lost connection
and DNS. The zookeepe
