Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-26 Thread Joakim Hansson
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

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-26 Thread Ken Gaillot
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,

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-19 Thread Jan Pokorný
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: >> *

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-14 Thread Joakim Hansson
> > >> 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

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-14 Thread Kristoffer Grönlund
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,

[ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-12 Thread Joakim Hansson
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 wait 2 minutes after tomcat is

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-12 Thread Kristoffer Grönlund
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

Re: [ClusterLabs] Wait until resource is really ready before moving clusterip

2016-01-12 Thread Ken Gaillot
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