On Thu, Aug 4, 2011 at 4:28 PM, Ulrich Windl
wrote:
Dan Frincu schrieb am 03.08.2011 um 13:28 in
> Nachricht
> :
>> Hi,
>>
>> On Wed, Aug 3, 2011 at 2:22 PM, wrote:
>> > Hi & Thanks
>> >
>> > I don't think the 1000 or 5000 value makes any difference,
>>
>> The values make little difference
>>> Dan Frincu schrieb am 03.08.2011 um 13:28 in
Nachricht
:
> Hi,
>
> On Wed, Aug 3, 2011 at 2:22 PM, wrote:
> > Hi & Thanks
> >
> > I don't think the 1000 or 5000 value makes any difference,
>
> The values make little difference, it's about having a higher score atm.
Hi!
Isn't the stickyne
Hi Yan,
> Pushed. Since we don't have a separate branch, you might need to
> back-port this patch to pacemaker-mgmt-2.0.0, which is compatible with
> pacemaker-1.0.x
Thanks!!
However, we need the release of pacemaker-mgmt for Pacemaker1.0.
Is it impossible you apply a patch to a repository of p
Permission problem perhaps? Not really sure what you're doing but the
fact that you have users configuring the cluster (why do you do this
btw?) may be pointing to a permission issue.
-mgb
On 11-08-03 06:57 PM, Rahul Kanna wrote:
> Hi,
>
> Our system setup:
>
> Heartbeat 3.0.3
> DRBD (to manage
Hi,
Our system setup:
Heartbeat 3.0.3
DRBD (to manage file system and it is one of the resource managed by CRM)
Redhat Linux
Pacemaker
We have built an application on top of Linux-HA for users to configure
cluster by giving IP addresses of the nodes, do operations like Restart
system, Change hos
Hi,
On Wed, Aug 3, 2011 at 5:23 PM, wrote:
> Hi
>
> When we do a crm resource migrate resource-name, crm add a cli-preference
> in the configuration for
> this resource.
> I wonder if there is a way to tell Pacemaker that, once the resource is
> running on the new target node, it could automatic
Hi
When we do a crm resource migrate resource-name, crm add a cli-preference
in the configuration for
this resource.
I wonder if there is a way to tell Pacemaker that, once the resource is
running on the new target node, it could automatically remove the
cli-preference ?
or for example after a g
Hi,
On Wed, Aug 3, 2011 at 3:00 PM, wrote:
> Hi,
>
> knowing that res1-[1-3] are in group-1 and res2-[1-3] are in group-2, the
> crm_verify -L 2>&1 | grep stick displays:
>
> debug: unpack_config: Default stickiness: 5000
> debug: common_apply_stickiness: Resource clone-1:0: preferring curre
Hi Hideo,
On 08/02/11 09:14, renayama19661...@ybb.ne.jp wrote:
> Hi Yan,
>
> I confirmed that a trap was transmitted with a patch definitely.
OK, thanks!
>
> We request that we apply a patch to each pacemaker-mgmt of pacemaker1.0 and
> pacemaker1.1.
Pushed. Since we don't have a separate branc
Hi,
knowing that res1-[1-3] are in group-1 and res2-[1-3] are in group-2, the
crm_verify -L 2>&1 | grep stick displays:
debug: unpack_config: Default stickiness: 5000
debug: common_apply_stickiness: Resource clone-1:0: preferring current
location (node=node2, weight=1)
debug: common_apply_s
Hi,
On Wed, Aug 3, 2011 at 2:22 PM, wrote:
> Hi & Thanks
>
> I don't think the 1000 or 5000 value makes any difference,
The values make little difference, it's about having a higher score atm.
> so the rsc_options could make it work ?
Yes, I believe so.
> But do you have also the order with
Hi & Thanks
I don't think the 1000 or 5000 value makes any difference,
so the rsc_options could make it work ?
But do you have also the order with a clone ?
Because on other of my configurations, I have also
property $id="cib-bootstrap-options" \
default-resource-stickiness="5000"
and the
Hi,
On Tue, Aug 2, 2011 at 6:06 PM, wrote:
> Hi
>
> I have this simple configuration of locations and orders between resources
> group-1 , group-2 and clone-1
> (on a two nodes ha cluster with Pacemaker-1.1.2-7 /corosync-1.2.3-21) :
>
> location loc1-group-1 group-1 +100: node2
> location loc1
13 matches
Mail list logo
