Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Zookeeper >> mail # user >> forceSync=no

Copy link to this message
Re: forceSync=no
For a single node failure I believe so.


On Thu, Jun 14, 2012 at 11:56 AM, Raj N <[EMAIL PROTECTED]> wrote:
> Sorry, I should have been more specific. By corrupt, I mean that the
> zookeeper node doesn't come back up on a restart. I would have imagined
> that zookeeper would sync the lost transactions from its peers. I agree I
> will have a problem if I have multiple failures. But for a single node
> failure in a 3-node ensemble, I should be able to recover even if
> forceSync=no.
> Thanks
> -Raj
> On Thu, Jun 14, 2012 at 1:03 PM, Jonathan Simms <[EMAIL PROTECTED]> wrote:
>> There's a big warning in the documentation that says that's a possibility.
>> If you don't force both Java and the OS to flush their IO buffers to disk,
>> then you have no guarantees that your data is consistent.
>> On 6/14/12 10:56 AM, "Raj N" <[EMAIL PROTECTED]> wrote:
>> >Are you guys aware of any issues with forceSync=no that could cause the
>> >transaction log to get corrupted on a zookeeper crash.
>> >
>> >Thanks
>> >-Raj