Re: File access pattern on HDFS?

sure, one option (maybe not a very scalable one) is to register a URL with the namenode. The NN can then post a batch of transactions as a POST to the specified URL. another option would be to write the file-change-log to a well-known hdfs file itself. thanks dhruba On Mon, Mar 7, 2011 at 1:05

Hadoop-Common-trunk-Commit - Build # 521 - Still Failing

See https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/521/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 2022 lines...] [exec] libtool: instal

Hadoop-Common-trunk-Commit - Build # 520 - Still Failing

See https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/520/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 2037 lines...] clean-sign: sign: signan

Re: Massive checkin to hadoop-0.20-security-patches

Is there any plan to put back v1 of the metrics system? This has been removed out from branch-0.20-security. Downstream projects are depending on v1 of metrics system are unable to integrate with Hadoop 0.20-security branch. The affected projects includes HBase and Chukwa. It would be nice i

[jira] Created: (HADOOP-7171) Support UGI in FileContext API

Support UGI in FileContext API -- Key: HADOOP-7171 URL: https://issues.apache.org/jira/browse/HADOOP-7171 Project: Hadoop Common Issue Type: Bug Components: security Reporter: Owen O'Malley

[jira] Created: (HADOOP-7170) Support UGI in FileContext API

Support UGI in FileContext API -- Key: HADOOP-7170 URL: https://issues.apache.org/jira/browse/HADOOP-7170 Project: Hadoop Common Issue Type: Bug Components: security Reporter: Owen O'Malley

Re: Massive checkin to hadoop-0.20-security-patches

On Mar 4, 2011, at 9:08 AM, Rottinghuis, Joep wrote: As far as I know, the pushes are done. The branching picture looks roughly like: +---+-> branch-0.20-security \ \

[jira] Created: (HADOOP-7169) Allow using a file to exclude certain tests from build

Allow using a file to exclude certain tests from build -- Key: HADOOP-7169 URL: https://issues.apache.org/jira/browse/HADOOP-7169 Project: Hadoop Common Issue Type: Improvement Affects

[jira] Created: (HADOOP-7168) Allow using a file to exclude certain tests from build

Allow using a file to exclude certain tests from build -- Key: HADOOP-7168 URL: https://issues.apache.org/jira/browse/HADOOP-7168 Project: Hadoop Common Issue Type: Improvement Affects

[jira] Created: (HADOOP-7167) Allow using a file to exclude certain tests from build

Allow using a file to exclude certain tests from build -- Key: HADOOP-7167 URL: https://issues.apache.org/jira/browse/HADOOP-7167 Project: Hadoop Common Issue Type: Improvement Affects

[jira] Created: (HADOOP-7166) DaemonFactory should be moved from HDFS to common

DaemonFactory should be moved from HDFS to common - Key: HADOOP-7166 URL: https://issues.apache.org/jira/browse/HADOOP-7166 Project: Hadoop Common Issue Type: Improvement Reporter:

Re: File access pattern on HDFS?

HDFS-1179: is exactly what I was looking for. Would it be a good idea to transmit info over TCP/UDP? --- Gautam On Mon, Mar 7, 2011 at 11:46 AM, Dhruba Borthakur wrote: > Here is a JIRA that talks about a file-change-log (but no work has been > done > yet) > > http://issues.apache.org/jira/brow

Re: File access pattern on HDFS?

Here is a JIRA that talks about a file-change-log (but no work has been done yet) http://issues.apache.org/jira/browse/HDFS-1179 thanks, dhruba On Mon, Mar 7, 2011 at 1:24 AM, Harsh J wrote: > There is no such information (history of atime changes, although atime > is held for every file in th

Re: File access pattern on HDFS?

There is no such information (history of atime changes, although atime is held for every file in the NN) held by the NameNode right now. I think HDFS-782 is slightly relevant to maintaining a 'hot-zone' info, although at a block level and among datanodes. I couldn't find a jira that talks about kee