Re: RollingUpgrade Rollback openfiles issue

2017-05-26 Thread Vinayakumar B
hdfs-dev@hadoop.apache.org> Sent: Friday, May 26, 2017 5:05 AM Subject: RE: RollingUpgrade Rollback openfiles issue Thanks Kihwal, Found another case, which looks more dangerous. 1. File written and closed. FINALIZED block in DN. 2. Rolling upgrade started. 3. File re-opened for append,

Re: RollingUpgrade Rollback openfiles issue

2017-05-26 Thread Kihwal Lee
Kihwal From: Vinayakumar B To: Kihwal Lee ; "hdfs-dev@hadoop.apache.org" Sent: Friday, May 26, 2017 5:05 AM Subject: RE: RollingUpgrade Rollback openfiles issue Thanks Kihwal, Found another case, which looks more dangerous. 1. File written and closed. FINALIZ

RE: RollingUpgrade Rollback openfiles issue

2017-05-26 Thread Vinayakumar B
considering these usecases. Any thoughts? -Vinay From: Kihwal Lee [mailto:kih...@yahoo-inc.com] Sent: 25 May 2017 22:16 To: Vinayakumar B ; hdfs-dev@hadoop.apache.org Subject: Re: RollingUpgrade Rollback openfiles issue Hi Vinay, If I rephrase the question, Does a RU rollback snapshot provide a

Re: RollingUpgrade Rollback openfiles issue

2017-05-25 Thread Kihwal Lee
inayakumar B To: "hdfs-dev@hadoop.apache.org" Sent: Thursday, May 25, 2017 8:10 AM Subject: RollingUpgrade Rollback openfiles issue Hi all, Have a doubt with expected behavior in case of RollingUpgrade and rollback. Scenario: 1. file was being written before rolling upgrade star

RollingUpgrade Rollback openfiles issue

2017-05-25 Thread Vinayakumar B
Hi all, Have a doubt with expected behavior in case of RollingUpgrade and rollback. Scenario: 1. file was being written before rolling upgrade started and written some bytes, say X, with hsync(). 2. Rolling upgrade done and writer continued to write and added some more bytes and file closed w