[jira] [Created] (HDFS-4939) Retain old edits log, don't retain all minimum required logs

Fengdong Yu created HDFS-4939: - Summary: Retain old edits log, don't retain all minimum required logs Key: HDFS-4939 URL: https://issues.apache.org/jira/browse/HDFS-4939 Project: Hadoop HDFS Iss

[jira] [Created] (HDFS-4938) Reduce redundant information in edit logs and image files

Arpit Agarwal created HDFS-4938: --- Summary: Reduce redundant information in edit logs and image files Key: HDFS-4938 URL: https://issues.apache.org/jira/browse/HDFS-4938 Project: Hadoop HDFS Iss

[jira] [Created] (HDFS-4937) ReplicationMonitor can infinite-loop in BlockPlacementPolicyDefault#chooseRandom()

Kihwal Lee created HDFS-4937: Summary: ReplicationMonitor can infinite-loop in BlockPlacementPolicyDefault#chooseRandom() Key: HDFS-4937 URL: https://issues.apache.org/jira/browse/HDFS-4937 Project: Hadoo

Re: A question for txid

Thanks Harsh,Todd. After 200 million years, spacemen manage the earth, they also know Hadoop, but they cannot restart it, after a hard debug they find the txid has been overflowed for many years. --Send from my Sony mobile. On Jun 25, 2013 10:52 PM, "Todd Lipcon" wrote: > I did some back of the

[jira] [Resolved] (HDFS-4936) Handle overflow condition for txid going over Long.MAX_VALUE

[ https://issues.apache.org/jira/browse/HDFS-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-4936. --- Resolution: Not A Problem > Handle overflow condition for txid going over Long.MAX_VALUE > ---

Re: A question for txid

I did some back of the envelope math when implementing txids, and determined that overflow is not ever going to happen... A "busy" namenode does 1000 write transactions/second (2^10). MAX_LONG is 2^63. So, we can run for 2^63 seconds. A year is about 2^25 seconds. So, at 1k tps, you can run your na

Re: A question for txid

Yes, it logically can if there have been as many transactions (its a very very large number to reach though). Long.MAX_VALUE is (2^63 - 1) or 9223372036854775807. I hacked up my local NN's txids manually to go very large (close to max) and decided to try out if this causes any harm. I basically b

[jira] [Created] (HDFS-4936) Handle overflow condition for txid going over Long.MAX_VALUE

Harsh J created HDFS-4936: - Summary: Handle overflow condition for txid going over Long.MAX_VALUE Key: HDFS-4936 URL: https://issues.apache.org/jira/browse/HDFS-4936 Project: Hadoop HDFS Issue Type:

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

See Changes: [cnauroth] HDFS-4927. CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode. Contributed by Chris Nauroth. [cmccabe] HADOOP-9355. Abstract symlink tests to use either FileCon

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

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1441/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 11234 lines...] [WARNING] Failed to retrieve plugin descr

[jira] [Created] (HDFS-4934) add symlink support to WebHDFS server side

Alejandro Abdelnur created HDFS-4934: Summary: add symlink support to WebHDFS server side Key: HDFS-4934 URL: https://issues.apache.org/jira/browse/HDFS-4934 Project: Hadoop HDFS Issue Ty

[jira] [Created] (HDFS-4935) add symlink support to HttpFS server side

Alejandro Abdelnur created HDFS-4935: Summary: add symlink support to HttpFS server side Key: HDFS-4935 URL: https://issues.apache.org/jira/browse/HDFS-4935 Project: Hadoop HDFS Issue Typ

[jira] [Created] (HDFS-4933) add symlink support to WebHDFS to HTTP REST API & client filesystem

Alejandro Abdelnur created HDFS-4933: Summary: add symlink support to WebHDFS to HTTP REST API & client filesystem Key: HDFS-4933 URL: https://issues.apache.org/jira/browse/HDFS-4933 Project: Hado

Jenkins build became unstable: Hadoop-Hdfs-0.23-Build #649

See

Hadoop-Hdfs-0.23-Build - Build # 649 - Unstable

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/649/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 11842 lines...] [INFO] [INFO] --- maven-source-plugi

[jira] [Created] (HDFS-4932) Avoid a long line on the name node webUI if we have more Journal nodes

Fengdong Yu created HDFS-4932: - Summary: Avoid a long line on the name node webUI if we have more Journal nodes Key: HDFS-4932 URL: https://issues.apache.org/jira/browse/HDFS-4932 Project: Hadoop HDFS

A question for txid

Hi dear All, It's long type for the txid currently, FSImage.java: boolean loadFSImage(FSNamesystem target, MetaRecoveryContext recovery) throws IOException{ editLog.setNextTxId(lastAppliedTxId + 1L); } Is it possible that (lastAppliedTxId + 1L) exceed Long.MAX_VALUE ?