You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Shashikant Banerjee (Jira)" <ji...@apache.org> on 2021/04/09 06:13:00 UTC
[jira] [Created] (HDFS-15961) standby namenode failed to start
ordered snapshot deletion is enabled while having snapshottable directories
Shashikant Banerjee created HDFS-15961:
------------------------------------------
Summary: standby namenode failed to start ordered snapshot deletion is enabled while having snapshottable directories
Key: HDFS-15961
URL: https://issues.apache.org/jira/browse/HDFS-15961
Project: Hadoop HDFS
Issue Type: Sub-task
Components: snapshots
Affects Versions: 3.4.0
Reporter: Shashikant Banerjee
Assignee: Shashikant Banerjee
Fix For: 3.4.0
{code:java}
2021-04-08 12:07:25,398 INFO org.apache.hadoop.hdfs.server.blockmanagement.DatanodeDescriptor: Adding new storage ID DS-515dfb62-9975-4a2d-8384-d33ac8ff9cd1 for DN 172.27.121.195:9866
2021-04-08 12:07:55,581 INFO org.apache.hadoop.util.ExitUtil: Exiting with status 1: Could not provision Trash directory for existing snapshottable directories. Exiting Namenode.
2021-04-08 12:07:55,596 INFO org.apache.ranger.audit.provider.AuditProviderFactory: ==> JVMShutdownHook.run()
2021-04-08 12:07:55,596 INFO org.apache.ranger.audit.provider.AuditProviderFactory: JVMShutdownHook: Signalling async audit cleanup to start.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org