[jira] [Created] (HDFS-2360) Ugly stacktrace when quota exceeds

Ugly stacktrace when quota exceeds -- Key: HDFS-2360 URL: https://issues.apache.org/jira/browse/HDFS-2360 Project: Hadoop HDFS Issue Type: Bug Components: hdfs client Affects Versions: 0.23.0

[jira] [Created] (HDFS-2359) NPE found in Namenode log while Disk failed during distcp

NPE found in Namenode log while Disk failed during distcp -- Key: HDFS-2359 URL: https://issues.apache.org/jira/browse/HDFS-2359 Project: Hadoop HDFS Issue Type: Bug Componen

[jira] [Created] (HDFS-2358) NPE when core-site.xml is misconfirued with hos:port is missing in the default filesystem's uri

NPE when core-site.xml is misconfirued with hos:port is missing in the default filesystem's uri --- Key: HDFS-2358 URL: https://issues.apache.org/jira/browse/HDFS-2358

Re: corrupted edits log after power failure

Hi Gabi, I'd be a bit scared of that backup strategy; what happens if the TCP connection gets cut suddenly during curl? What happens if there's a TCP corruption? Such things have happened before. Personally, we have the SNN merge the edits every 15 minutes. If it hasn't happened in 30 minut

Re: corrupted edits log after power failure

Does the backup process include syncing? On-drive write cache can also trick you. For absolutely critical data, it is a good idea to use a controller with battery-backed write cache or a service/product that guarantees durability. Kihwal On 9/22/11 3:48 AM, "Gabi Kazav" wrote: Hi, I had Powe

corrupted edits log after power failure

Hi, I had Power Failure. I have backup of files: edits, fsimage. I am backing it up with: curl -s http://nameNode:50070/getimage?getimage=1 > fsimage curl -s http://nameNode:50070/getimage?getedits=1 > edits When I am trying to start the HDFS with the recovered files, I got error about the edi

[jira] [Resolved] (HDFS-2357) app master configuration web UI link under the Job menu opens up application menu

[ https://issues.apache.org/jira/browse/HDFS-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves resolved HDFS-2357. - Resolution: Invalid closing because I accidentally filed this in hdfs instead of mapreduce. > app

[jira] [Created] (HDFS-2357) app master configuration web UI link under the Job menu opens up application menu

app master configuration web UI link under the Job menu opens up application menu - Key: HDFS-2357 URL: https://issues.apache.org/jira/browse/HDFS-2357 Project: Hadoop HD

Hadoop-Hdfs-0.23-Build - Build # 17 - Still Unstable

See https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/17/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9502 lines...] main: [INFO] Executed tasks [INFO] [I

Jenkins build is still unstable: Hadoop-Hdfs-0.23-Build #17

See

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

See Changes: [szetszwo] HDFS-46. Change default namespace quota of root directory from Integer.MAX_VALUE to Long.MAX_VALUE. Contributed by Uma Maheswara Rao G [vinodkv] MAPREDUCE-3048. Fixed test-patch to run tests via "mvn clean in

Hadoop-Hdfs-trunk - Build # 808 - Failure

See https://builds.apache.org/job/Hadoop-Hdfs-trunk/808/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 9859 lines...] [INFO] There are 9341 checkstyle errors. [W

[jira] [Created] (HDFS-2356) webhdfs: support case insensitive query parameter names

webhdfs: support case insensitive query parameter names --- Key: HDFS-2356 URL: https://issues.apache.org/jira/browse/HDFS-2356 Project: Hadoop HDFS Issue Type: Sub-task Reporte