You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@zookeeper.apache.org by Kathryn Hogg <Ka...@oati.net> on 2018/01/25 14:00:23 UTC
transaction log directory on VM
If we are running zookeeper on virtual machines, what is the recommended best practice in regards to the transaction log directory? We can create a dedicated virtual disk for the transaction logs but what if that vdi/vmdk file is sitting on the same drive on the host OS?
--
Kathryn Hogg
Open Access Technology International, Inc.
3660 Technology Drive NE, Minneapolis, MN 55418
CONFIDENTIAL INFORMATION: This email and any attachment(s) contain confidential and/or proprietary information of Open Access Technology International, Inc. Do not copy or distribute without the prior written consent of OATI. If you are not named a recipient to the message, please notify the sender immediately and do not retain the message in any form, printed or electronic.
Re: transaction log directory on VM
Posted by Andor Molnar <an...@cloudera.com>.
Hi Kathryn,
The only benefit I can think of is that transaction logs cannot steal space
from other parts of the system. e.g. root filesystem
Other than that it should be on a physically different drive for
performance gain.
Andor
On Thu, Jan 25, 2018 at 3:57 PM, Page, Jeremy <je...@gilbarco.com>
wrote:
> There are still reasons to keep it on an isolated file system, although
> it's not as important as if you have multiple physical disks (especially if
> they're spinning disks as opposed to SSDs).
>
> ________________________________
> From: Kathryn Hogg <Ka...@oati.net>
> Sent: Thursday, January 25, 2018 9:00 AM
> To: user@zookeeper.apache.org
> Subject: transaction log directory on VM
>
> If we are running zookeeper on virtual machines, what is the recommended
> best practice in regards to the transaction log directory? We can create a
> dedicated virtual disk for the transaction logs but what if that vdi/vmdk
> file is sitting on the same drive on the host OS?
>
> --
> Kathryn Hogg
> Open Access Technology International, Inc.
> 3660 Technology Drive NE, Minneapolis, MN 55418
>
> CONFIDENTIAL INFORMATION: This email and any attachment(s) contain
> confidential and/or proprietary information of Open Access Technology
> International, Inc. Do not copy or distribute without the prior written
> consent of OATI. If you are not named a recipient to the message, please
> notify the sender immediately and do not retain the message in any form,
> printed or electronic.
>
> ________________________________
>
> Please be advised that this email may contain confidential information. If
> you are not the intended recipient, please notify us by email by replying
> to the sender and delete this message. The sender disclaims that the
> content of this email constitutes an offer to enter into, or the acceptance
> of, any agreement; provided that the foregoing does not invalidate the
> binding effect of any digital or other electronic reproduction of a manual
> signature that is included in any attachment.
>
Re: transaction log directory on VM
Posted by "Page, Jeremy" <je...@gilbarco.com>.
There are still reasons to keep it on an isolated file system, although it's not as important as if you have multiple physical disks (especially if they're spinning disks as opposed to SSDs).
________________________________
From: Kathryn Hogg <Ka...@oati.net>
Sent: Thursday, January 25, 2018 9:00 AM
To: user@zookeeper.apache.org
Subject: transaction log directory on VM
If we are running zookeeper on virtual machines, what is the recommended best practice in regards to the transaction log directory? We can create a dedicated virtual disk for the transaction logs but what if that vdi/vmdk file is sitting on the same drive on the host OS?
--
Kathryn Hogg
Open Access Technology International, Inc.
3660 Technology Drive NE, Minneapolis, MN 55418
CONFIDENTIAL INFORMATION: This email and any attachment(s) contain confidential and/or proprietary information of Open Access Technology International, Inc. Do not copy or distribute without the prior written consent of OATI. If you are not named a recipient to the message, please notify the sender immediately and do not retain the message in any form, printed or electronic.
________________________________
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.