[jira] [Created] (HDFS-4331) checkpoint between NN and SNN (secure cluster) does not happen once NN TGT expires

Benoy Antony created HDFS-4331: -- Summary: checkpoint between NN and SNN (secure cluster) does not happen once NN TGT expires Key: HDFS-4331 URL: https://issues.apache.org/jira/browse/HDFS-4331 Project:

[jira] [Created] (HDFS-4330) Support snapshots up to the snapshot limit

Tsz Wo (Nicholas), SZE created HDFS-4330: Summary: Support snapshots up to the snapshot limit Key: HDFS-4330 URL: https://issues.apache.org/jira/browse/HDFS-4330 Project: Hadoop HDFS

[jira] [Resolved] (HDFS-4103) Support O(1) snapshot creation

[ https://issues.apache.org/jira/browse/HDFS-4103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE resolved HDFS-4103. -- Resolution: Fixed Fix Version/s: Snapshot (HDFS-2802) Hadoop Flags: R

[jira] [Resolved] (HDFS-4320) Add a separate configuration for namenode rpc address instead of using fs.default.name

[ https://issues.apache.org/jira/browse/HDFS-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-4320. --- Resolution: Fixed Fix Version/s: 1.2.0 Hadoop Flags: Reviewed I committed the patc

[jira] [Created] (HDFS-4329) DFSShell issues with directories with spaces in name

Andy Isaacson created HDFS-4329: --- Summary: DFSShell issues with directories with spaces in name Key: HDFS-4329 URL: https://issues.apache.org/jira/browse/HDFS-4329 Project: Hadoop HDFS Issue Ty

Re: FSDataInputStream.read returns -1 with growing file and never continues reading

Thank you, Harsh. I appreciate it. 2012/12/20 Harsh J > Hi Christoph, > > If you use sync/hflush/hsync, the new length of data is only seen by a > new reader, not an existent reader. The "workaround" you've done > exactly how we've implemented the "fs -tail " utility. See code > for that at > ht

Re: FSDataInputStream.read returns -1 with growing file and never continues reading

Hi Christoph, If you use sync/hflush/hsync, the new length of data is only seen by a new reader, not an existent reader. The "workaround" you've done exactly how we've implemented the "fs -tail " utility. See code for that at http://svn.apache.org/viewvc/hadoop/common/trunk/hadoop-common-project/

Build failed in Jenkins: Hadoop-Hdfs-trunk #1260

See Changes: [llu] Update CHANGES.txt separately for clean cherry-picks. [llu] YARN-223. Update process tree instead of getting new process trees. (Radim Kolar via llu) [cutting] MAPREDUCE-4887. Add RehashPartitioner, to smooth dis

Hadoop-Hdfs-trunk - Build # 1260 - Still Failing

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1260/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9750 lines...] Tests run: 7, Failures: 0, Errors: 0, Skip

FSDataInputStream.read returns -1 with growing file and never continues reading

Hi, I am experiencing an unexpected situation where FSDataInputStream.read() returns -1 while reading data from a file that another process still appends to. According to the documentation read() should never return -1 but throw Exceptions on errors. In addition, there's more data available, and r

Re: Recovering fsImage from Namenode Logs

Unfortunately, the checkpoint image that I have has the deletes recorded. I cannot use it. I do have an image that is 15 days old, which I am currently running. I looked at the my logs and I have the filename, block allocated and generation stamp. Can you explain to me the importance of the genera