[jira] Created: (HDFS-1494) Adding new target to build.xml to run test-core without compiling

Adding new target to build.xml to run test-core without compiling - Key: HDFS-1494 URL: https://issues.apache.org/jira/browse/HDFS-1494 Project: Hadoop HDFS Issue Type: New Feat

Build failed in Hudson: Hadoop-Hdfs-trunk #484

See Changes: [tomwhite] HDFS-1292. Allow artifacts to be published to the staging Apache Nexus Maven Repository. Contributed by Giridharan Kesavan. -- [...truncated 565625 lines...]

Re: Why datanode does a flush to disk after receiving a packet

Thanks Todd, In HDFS-6313, i see three API (sync, hflush, hsync), And I assume hflush corresponds to : *"API2: flushes out to all replicas of the block. The data is in the buffers of the DNs but not on the DN's OS buffers. New readers will see the data after the call has returned.*" I am still c

Re: Why datanode does a flush to disk after receiving a packet

On Thu, Nov 11, 2010 at 7:31 AM, Thanh Do wrote: > Thanks Todd, > > In HDFS-6313, i see three API (sync, hflush, hsync), > And I assume hflush corresponds to : > > *"API2: flushes out to all replicas of the block. > The data is in the buffers of the DNs but not on the DN's OS buffers. > New reade

Re: Why datanode does a flush to disk after receiving a packet

A few clarification on API2 semantics. 1. Ack gets sent back to the client before a packet gets written to local files. 2. Data become visible to new readers on the condition that at least one DataNode does not have an error. 3. The reason that flush is done after a write is more for the purpose o

Re: Why datanode does a flush to disk after receiving a packet

On Thu, Nov 11, 2010 at 11:55 AM, Hairong Kuang wrote: > A few clarification on API2 semantics. > > 1. Ack gets sent back to the client before a packet gets written to local > files. > Ah, I see in trunk this is the case. In 0.20-append, it's the other way around - we only enqueue after flush.

Re: Why datanode does a flush to disk after receiving a packet

Thank you all for clarification guys. I also looked at 0.20-append trunk and see that the order is totally different. One more thing, do you guys plan to implement hsync(), i.e API3 in the near future. Are there any class of application that requires such strong guarantee? Thanh On Thu, Nov 11,

Re: Why datanode does a flush to disk after receiving a packet

On Thu, Nov 11, 2010 at 12:43 PM, Thanh Do wrote: > Thank you all for clarification guys. > I also looked at 0.20-append trunk and see that the order is totally > different. > > One more thing, do you guys plan to implement hsync(), i.e API3 > in the near future. Are there any class of applicatio

Re: Why datanode does a flush to disk after receiving a packet

Got it! Currently, the model is single writer/multiple reader. In the GFS paper, i see they have *record append* semantics, that is allow multiple clients writing to the same file. Do you guys have any plan to implement this... Thanh On Thu, Nov 11, 2010 at 3:10 PM, Todd Lipcon wrote: > On Thu

Re: Why datanode does a flush to disk after receiving a packet

On Thu, Nov 11, 2010 at 1:26 PM, Thanh Do wrote: > Got it! > > Currently, the model is single writer/multiple reader. > In the GFS paper, i see they have *record append* > semantics, that is allow multiple clients writing to the > same file. Do you guys have any plan to implement > this... > > No

[jira] Created: (HDFS-1495) HDFS does not properly check permissions of files in a directory when doing rmr

HDFS does not properly check permissions of files in a directory when doing rmr --- Key: HDFS-1495 URL: https://issues.apache.org/jira/browse/HDFS-1495 Project: Hadoop HDFS

[jira] Created: (HDFS-1496) TestStorageRestore is failing after HDFS-903 fix

TestStorageRestore is failing after HDFS-903 fix Key: HDFS-1496 URL: https://issues.apache.org/jira/browse/HDFS-1496 Project: Hadoop HDFS Issue Type: Bug Components: test