On 06/23/2016 04:57 AM, Lentes, Bernd wrote:
>
> What i mean with "less complicated" is that i prefer to have everything
> managed by pacemaker and not some stuff by pacemaker and some stuff by init.
> This is more overseeable.
I'd agree to that except I am regularly locking up
- On Jun 22, 2016, at 11:48 PM, Dimitri Maziuk dmaz...@bmrb.wisc.edu wrote:
> On 06/22/2016 04:29 PM, Klaus Wenninger wrote:
>> On 06/22/2016 11:17 PM, Lentes, Bernd wrote:
>
>>> I'm thinking about active/active. But i think active/passive with a
>>> non-cluster fs is less complicated.
>>
On 06/22/2016 04:29 PM, Klaus Wenninger wrote:
> On 06/22/2016 11:17 PM, Lentes, Bernd wrote:
>> I'm thinking about active/active. But i think active/passive with a
>> non-cluster fs is less complicated.
> But you will need something to control DRBD - especially in the
> active/passive-case.
>
On 06/22/2016 11:17 PM, Lentes, Bernd wrote:
>
> Ursprüngliche Nachricht
> Von: Dimitri Maziuk <dmaz...@bmrb.wisc.edu>
> Datum: 22.06.2016 21:23 (GMT+01:00)
> An: users@clusterlabs.org
> Betreff: Re: [ClusterLabs] design question to DRBD
>
> On 06/2
Ursprüngliche Nachricht
Von: Dimitri Maziuk <dmaz...@bmrb.wisc.edu>
Datum: 22.06.2016 21:23 (GMT+01:00)
An: users@clusterlabs.org
Betreff: Re: [ClusterLabs] design question to DRBD
On 06/22/2016 02:13 PM, Lentes, Bernd wrote:
>
> I'm thinking about s
On 06/22/2016 02:13 PM, Lentes, Bernd wrote:
>
> I'm thinking about starting drbd and the ocfs fs by init. I don't see the
> strong need having it controlled by pacemaker.
> But of course the mix is more difficult to maintain.
Are you going to use active-active drbd with a cluster filesystem?
- On Jun 22, 2016, at 8:34 PM, Dimitri Maziuk dmaz...@bmrb.wisc.edu wrote:
> On 06/22/2016 01:00 PM, Lentes, Bernd wrote:
>> - On Jun 22, 2016, at 7:17 PM, Dimitri Maziuk dmaz...@bmrb.wisc.edu
>> wrote:
>
>>> Does your webapp ever write to /srv/www?
>
>> it does.
>
> Yeah, OK, it
On 06/22/2016 01:00 PM, Lentes, Bernd wrote:
> - On Jun 22, 2016, at 7:17 PM, Dimitri Maziuk dmaz...@bmrb.wisc.edu wrote:
>> Does your webapp ever write to /srv/www?
> it does.
Yeah, OK, it that case you want DRBD so the writes go to both nodes at
once.
If you have to use DRBD anyway, then
- On Jun 22, 2016, at 7:17 PM, Dimitri Maziuk dmaz...@bmrb.wisc.edu wrote:
> On 06/22/2016 11:28 AM, Lentes, Bernd wrote:
>
>> yes, that's a good hint. I will not synchronize /usr/lib/perl with DRBD.
>> But for /srv/www it should be fine ?
>
> Does your webapp ever write to /srv/www? If
On 06/22/2016 11:28 AM, Lentes, Bernd wrote:
> yes, that's a good hint. I will not synchronize /usr/lib/perl with DRBD.
> But for /srv/www it should be fine ?
Does your webapp ever write to /srv/www? If not I would consider running
two copies of everything with ZFS as a backing store and
- On Jun 22, 2016, at 3:59 PM, Klaus Wenninger kwenn...@redhat.com wrote:
> On 06/22/2016 02:30 PM, Lentes, Bernd wrote:
>> Hi,
>>
>> we have a two node cluster. It is running a Web-Application. Web-Application
>> needs a MySQL Database, has static and dynamic (perlscripts) webpages.
>> I
On 22/06/16 08:30 AM, Lentes, Bernd wrote:
> Hi,
>
> we have a two node cluster. It is running a Web-Application. Web-Application
> needs a MySQL Database, has static and dynamic (perlscripts) webpages.
> I will make the DB HA with MySQL replication.
> From time to time it's likely that
Hi,
we have a two node cluster. It is running a Web-Application. Web-Application
needs a MySQL Database, has static and dynamic (perlscripts) webpages.
I will make the DB HA with MySQL replication.
From time to time it's likely that something in the webapp is changed, so we
have to edit some
13 matches
Mail list logo
