[HDFS-12016] Ozone: SCM: Container metadata are not loaded properly after datanode restart

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: HDFS-7240
• Fix Version/s: HDFS-7240
• Component/s: ozone, scm
• Target Version/s: HDFS-7240
• Hadoop Flags: Reviewed
• Assignee: Xiaoyu Yao
• Reporter: Nandakumar
• Created: 23/Jun/17 00:13
• Updated: 26/Apr/18 21:51
• Resolved: 23/Jun/17 21:40

Description

Repro steps (Credit to nandakumar131)
1. create volume/bucket/key
2. putkey
3. restart DN
4. getkey will hit error on container not found like below.

2017-06-22 15:28:29,950 [Thread-48] INFO  (OzoneExceptionMapper.java:39)  vol-2/bucket-1/key-1 xyao 8727acc4-c1e9-4ba3-a819-4c0e16957079 - Returning exception. ex: {"httpCode":500,"shortMessage":"internalServerError","resource":"xyao","message":"org.apache.hadoop.scm.container.common.helpers.StorageContainerException: Unable to find the container. Name: 48cb0c3d-0537-4cff-b716-a7f69ebf50bc","requestID":"8 

The root cause is OzoneContainer#OzoneContainer does not load containers from repository properly when ozone.container.metadata.dirs are specified.

The fix is to append the CONTAINER_ROOT_PREFIX when looking for containers on the datanode.

Issue Links

• is related to: HDFS-11844 Ozone: Recover SCM state when SCM is restarted