Aww, thanks for the kind words to close it out :). Glad to hear it's
worked well for you.
Just to share some Kerberos knowledge (and dispel any misinformation),
any application which stops working after the default ticket lifetime is
"doing it wrong" (tm). Like Steve pointed out, this is why r
Talat,
I don't have much understanding of the Selenium Grid application. However you
can run it on a Hadoop cluster using Slider. All you need, is to create a
Slider app package.
Here is a guide and a sample Solr app-package that will help you to get started
-
http://slider.incubator.apache.or
Hi,
In my mapreduce application I use Selenium Grid. I wonder Is there any
possible way that Selenium Grid run on Hadoop cluster ? I want to find
a solution get more easy to manage resources. BTW They provide docker
images. [1]
Thanks
[1] https://github.com/SeleniumHQ/docker-selenium
--
Talat
Great! Thank you all.
Regarding 0.50, it's been a while, but I recall back porting a couple of
fixes to get my cluster up. IIRC, that was primarily related to kerberos
fixes for instantiating the cluster.
In 0.50 (+ the patches) accumulo and storm required a restart after 7
days. Barring that
> On 9 Mar 2016, at 13:59, Jon Maron wrote:
>
>>
>> On Mar 8, 2016, at 11:36 PM, Tim I wrote:
>>
>> Hi Josh,
>> Basically anything with a kerberos ticket could no longer could communicate
>> with anything else after 7 days due to the default config for the kerberos
>> server :
>> renew_lifeti
> On Mar 8, 2016, at 11:36 PM, Tim I wrote:
>
> Hi Josh,
> Basically anything with a kerberos ticket could no longer could communicate
> with anything else after 7 days due to the default config for the kerberos
> server :
> renew_lifetime = 7d
>
> The delegation token I believe was the reason