Hi,
how can I adjust the timeout for the start of a mysqld or a httpd in a config.
It seems to me as if this is a little to short for our systems.
One of my configuration looks like this:
crm(live)# configure show
node $id="18c3666b-ed2f-4dac-8aa7-59ff005b18de" nodename \
attributes stan
On Thu, Mar 07, 2013 at 11:09:03AM +1100, Andrew Beekhof wrote:
> If you put drbd into maintenance mode, we'd not perform any state
> changes (stop/stop/promote/demote) on it that could fail.
> That would likely do what you're after.
>
> On Thu, Mar 7, 2013 at 4:59 AM, Jan Škoda wrote:
> > Dne 6.
Le 11/03/2013 15:44, fatcha...@gmx.de a écrit :
Hi,
how can I adjust the timeout for the start of a mysqld or a httpd in a config.
It seems to me as if this is a little to short for our systems.
One of my configuration looks like this:
See
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crms
Hi,
On Sat, Mar 09, 2013 at 05:29:11PM +, Tim Small wrote:
> Hi,
>
> It looks to me like ocf:heartbeat:ManageVE might do the wrong thing in a
> couple of places, so I'd thought I'd check.
>
> The resource agent manages openvz containers (i.e. lightweight virtual
> machines AKA "VEs", think c
On 11/03/13 14:44, fatcha...@gmx.de wrote:
> how can I adjust the timeout for the start of a mysqld or a httpd in a
> config. It seems to me as if this is a little to short for our systems.
>
>
Change this:
> primitive Apache ocf:heartbeat:apache \
> params configfile="/etc/httpd/conf
On 11/03/13 15:12, Dejan Muhamedagic wrote:
>> A more flexible solution might be to make the timeout configurable, but
>> > in the absence of this, then I think upping the stop action timeout
>> > seems like the right thing to do.
>>
> The value you found is just an advice to the user. You can
On Sun, Mar 10, 2013 at 8:35 PM, Stefan Förster
wrote:
> Hello world,
>
> according to [1] using the pacemaker plugin with corosync is
> deprecated and will cease to be supported at some point in the future
> (on RHEL!).
A small but important distinction...
The plugin has never been supported on
On Mon, Mar 11, 2013 at 5:01 PM, Paul Sun wrote:
> Hi
>
>
>
> I am currently learning how to use pacemaker. I have created a three nodes
> configuration, and two IP resources. My target to setup the IP to follow
> only two nodes, and this is able to achieve by using the score in location
> command
Have a read of
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Clusters_from_Scratch/_perform_a_failover.html
On Sun, Mar 10, 2013 at 4:15 AM, jonas wrote:
>
> hi,
> I have build a 2 node test cluster on debian 6 withe an IP recourse. If
> I start both nodes the IP recourse starts up p
On Thu, Mar 7, 2013 at 5:30 PM, Vladislav Bogdanov wrote:
> 07.03.2013 03:37, Andrew Beekhof wrote:
>> On Thu, Mar 7, 2013 at 2:41 AM, Vladislav Bogdanov
>> wrote:
>>> 06.03.2013 08:35, Andrew Beekhof wrote:
>>
So basically, you want to be able to add/remove nodes from nodelist.*
in co
Hi, all
I am using the linux cluster. When I run "/etc/init.d/openais stop", I
found that
it just checks the status of corosync, if corosync exists, then it will
return.
Who can tell me why? openais does not make corosync exit?
Thanks a lot.
Zhu Yanjun
__
Hi
I have 3 nodes setup, and I have configured IP and LSB service. The LSB service
is relied on IP service. Given that I have startup node1 and node2, and then
node3 is started to join the cluster, it is found that the LSB service is
restarted on node2, is there any reason? I observed "Sending
12.03.2013 04:44, Andrew Beekhof wrote:
> On Thu, Mar 7, 2013 at 5:30 PM, Vladislav Bogdanov
> wrote:
>> 07.03.2013 03:37, Andrew Beekhof wrote:
>>> On Thu, Mar 7, 2013 at 2:41 AM, Vladislav Bogdanov
>>> wrote:
06.03.2013 08:35, Andrew Beekhof wrote:
>>>
> So basically, you want to be
13 matches
Mail list logo
