On Mon, 8 Jul 2019 19:27:00 +0200
Tiemen Ruiten wrote:
> On Mon, Jul 8, 2019 at 4:59 PM Jehan-Guillaume de Rorthais
> wrote:
>
> > On Mon, 8 Jul 2019 13:56:49 +0200
> > Tiemen Ruiten wrote:
> >
> > > Thank you for the clear explanation and advice.
> > >
> > > Hardware is adequate: 8x SSD
On Mon, Jul 8, 2019 at 4:59 PM Jehan-Guillaume de Rorthais
wrote:
> On Mon, 8 Jul 2019 13:56:49 +0200
> Tiemen Ruiten wrote:
>
> > Thank you for the clear explanation and advice.
> >
> > Hardware is adequate: 8x SSD and 20 cores per node, but I should note
> that
> > the filesystem is ZFS
On Mon, 8 Jul 2019 13:56:49 +0200
Tiemen Ruiten wrote:
> Thank you for the clear explanation and advice.
>
> Hardware is adequate: 8x SSD and 20 cores per node, but I should note that
> the filesystem is ZFS (stripe of mirrors) and there seems to be evidence
> that the way the WAL writer
On 05/07/19 03:50 +, Harvey Shepherd wrote:
> I was able to resolve an issue which caused these logs to disappear.
> The problem was that the LSB script was named "logging" and the
> daemon that it controlled was also called "logging". The init script
> uses "start-stop-daemon --name" to start
Hello.
I'm Donghyun Kim.
I work as a system engineer in Korea.
In the meantime, I was very interested in the cluster and want to promote
it in Korea.
There are many high-availability cases in Linux systems.
The reason why I am sending this mail is whether I can use the name
"ClusterLabs Korea"
Thank you for the clear explanation and advice.
Hardware is adequate: 8x SSD and 20 cores per node, but I should note that
the filesystem is ZFS (stripe of mirrors) and there seems to be evidence
that the way the WAL writer allocates space and ZFS' Copy-on-Write nature
don't play nice. A patch
