On 01/26/2016 05:06 AM, Joakim Hansson wrote:
> Thanks for the help guys.
> I ended up patching together my own RA from the Delay and Dummy RA's and
> using curl to request the header of solr's ping request handler on
> localhost, which made the resource start return a bit more dynamic.
> However,
Joakim Hansson writes:
> Notice how the tomcat-clone is started on node02 but the vIP remains
> stopped.
> If I start the fence agent on any of the other nodes the same thing happens
> (ie, vIP avoiding the fencing node)
> Any idea why this happens?
Hi,
I'm not 100% sure this is what is causing
Thanks for the help guys.
I ended up patching together my own RA from the Delay and Dummy RA's and
using curl to request the header of solr's ping request handler on
localhost, which made the resource start return a bit more dynamic.
However, now I have another problem which I don't think is relate
On 14/01/16 14:46 +0100, Kristoffer Grönlund wrote:
> Joakim Hansson writes:
>> When adding the Delay RA it starts throwing a bunch of errors and the
>> cluster starts fencing the nodes one by one.
>>
>> The error's I get with "pcs status":
>>
>> Failed Actions:
>> * Delay_monitor_0 on node03 'u
Joakim Hansson writes:
>
> When adding the Delay RA it starts throwing a bunch of errors and the
> cluster starts fencing the nodes one by one.
>
> The error's I get with "pcs status":
>
> Failed Actions:
> * Delay_monitor_0 on node03 'unknown error' (1): call=51, status=Timed Out,
> exit
> reaso
>
> >> Hi,
> >>
> >> There is the ocf:heartbeat:Delay resource agent, which on one hand is
> >> documented as a test resource, but on the other hand should do what you
> >> need:
> >>
> >> primitive solr ...
> >> primitive two-minute-delay ocf:heartbeat:Delay \
> >> params startdelay=120 meta tar
On 01/12/2016 07:57 AM, Kristoffer Grönlund wrote:
> Joakim Hansson writes:
>
>> Hi!
>> I have a cluster running tomcat which in turn run solr.
>> I use three nodes with loadbalancing via ipaddr2.
>> The thing is, when tomcat is started on a node it takes about 2 minutes
>> before solr is functio
Joakim Hansson writes:
> Hi!
> I have a cluster running tomcat which in turn run solr.
> I use three nodes with loadbalancing via ipaddr2.
> The thing is, when tomcat is started on a node it takes about 2 minutes
> before solr is functioning correctly.
>
> Is there a way to make the ipaddr2-clone