[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junping Du updated HDFS-8179:
-
Fix Version/s: 2.8.0
> DFSClient#getServerDefaults returns null within 1 hour of system start
> --
>
> Key: HDFS-8179
> URL: https://issues.apache.org/jira/browse/HDFS-8179
> Project: Hadoop HDFS
> Issue Type: Bug
>Affects Versions: 2.7.0
>Reporter: Xiaoyu Yao
>Assignee: Xiaoyu Yao
>Priority: Blocker
> Fix For: 2.8.0, 2.7.1, 3.0.0-alpha1
>
> Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch
>
>
> We recently hit NPE during Ambari Oozie service check. The failed hdfs
> command is below. It repros sometimes and then go away after the cluster runs
> for a while.
> {code}
> [ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
> /user/ambari-qa/mapredsmokeoutput
> rm: Failed to get server trash configuration: null. Consider using -skipTrash
> option
> {code}
> With additional tracing, the failure was located to the following stack.
> {code}
> 15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
> java.lang.NullPointerException
> at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
> at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
> at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
> at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
> at
> org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
> at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
> at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
> at
> org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
> at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
> at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
> at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
> rm: Failed to get server trash configuration: null. Consider using -skipTrash
> option
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-8179:
-
Attachment: HDFS-9179.dal.patch
Attach the Dal patch.
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch,
HDFS-9179.dal.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-8179:
-
Attachment: (was: HDFS-8179.dal.patch)
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-8179:
-
Attachment: HDFS-8179.dal.patch
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch,
HDFS-8179.dal.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-8179:
-
Attachment: (was: HDFS-9179.dal.patch)
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch,
HDFS-8179.dal.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jitendra Nath Pandey updated HDFS-8179:
---
Status: Open (was: Patch Available)
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-8179:
Resolution: Fixed
Fix Version/s: 2.7.1
Target Version/s: (was: 2.7.1)
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk, branch-2 and branch-2.7.
Thanks for the review [~jnp].
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Fix For: 2.7.1
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jitendra Nath Pandey updated HDFS-8179:
---
Status: Patch Available (was: Open)
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-8179:
-
Attachment: HDFS-8179.01.patch
Add a unit test for getServerDefaults().
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch, HDFS-8179.01.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-8179:
-
Attachment: HDFS-8179.00.patch
Attach a patch that fixed the DFSClient#getServerDefaults() to initialize
serverDefaults appropriately and added additional tracing at WARN level for
Trash policy related failures to make future investigation easier.
I've built private hadoop-common and hadoop-hdfs jars with the patch and
verified it fixed the issue on the machine with the original repro. No new test
is added because it is not easy to do physical machine restart in the unit test.
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDFS-8179:
-
Affects Version/s: 2.7.0
Status: Patch Available (was: Open)
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 2.7.0
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
Attachments: HDFS-8179.00.patch
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-8179:
Summary: DFSClient#getServerDefaults returns null within 1 hour of system
start (was: DFSClient#getServerDefaults returns null within 1 hour of NN start)
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-8179:
Priority: Blocker (was: Major)
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-8179) DFSClient#getServerDefaults returns null within 1 hour of system start
[
https://issues.apache.org/jira/browse/HDFS-8179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal updated HDFS-8179:
Target Version/s: 2.7.1
DFSClient#getServerDefaults returns null within 1 hour of system start
--
Key: HDFS-8179
URL: https://issues.apache.org/jira/browse/HDFS-8179
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Xiaoyu Yao
Assignee: Xiaoyu Yao
Priority: Blocker
We recently hit NPE during Ambari Oozie service check. The failed hdfs
command is below. It repros sometimes and then go away after the cluster runs
for a while.
{code}
[ambari-qa@c6401 ~]$ hadoop --config /etc/hadoop/conf fs -rm -r
/user/ambari-qa/mapredsmokeoutput
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
With additional tracing, the failure was located to the following stack.
{code}
15/04/17 20:57:12 DEBUG fs.Trash: Failed to get server trash configuration
java.lang.NullPointerException
at org.apache.hadoop.fs.Trash.moveToAppropriateTrash(Trash.java:86)
at org.apache.hadoop.fs.shell.Delete$Rm.moveToTrash(Delete.java:117)
at org.apache.hadoop.fs.shell.Delete$Rm.processPath(Delete.java:104)
at org.apache.hadoop.fs.shell.Command.processPaths(Command.java:321)
at
org.apache.hadoop.fs.shell.Command.processPathArgument(Command.java:293)
at org.apache.hadoop.fs.shell.Command.processArgument(Command.java:275)
at org.apache.hadoop.fs.shell.Command.processArguments(Command.java:259)
at
org.apache.hadoop.fs.shell.Command.processRawArguments(Command.java:205)
at org.apache.hadoop.fs.shell.Command.run(Command.java:166)
at org.apache.hadoop.fs.FsShell.run(FsShell.java:287)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
at org.apache.hadoop.fs.FsShell.main(FsShell.java:340)
rm: Failed to get server trash configuration: null. Consider using -skipTrash
option
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
