[HDDS-4108] ozone debug ldb scan without arguments results in core dump

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: Tools
• Target Version/s: 1.1.0
• Assignee: Attila Doroszlai
• Reporter: Attila Doroszlai
• Created: 12/Aug/20 07:55
• Updated: 12/Aug/20 17:27
• Resolved: 12/Aug/20 17:27

Description

Running ozone debug ldb scan without arguments results in core dump.

ozone debug ldb scan

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f13aff4ae71, pid=646, tid=669
#
# JRE version: OpenJDK Runtime Environment (11.0.7+10) (build 11.0.7+10-LTS)
# Java VM: OpenJDK 64-Bit Server VM (11.0.7+10-LTS, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x5d0e71]  AccessInternal::PostRuntimeDispatch<G1BarrierSet::AccessBarrier<1097844ul, G1BarrierSet>, (AccessInternal::BarrierType)2, 1097844ul>::oop_access_barrier(void*)+0x1
#
# Core dump will be written. Default location: /opt/hadoop/core
#
# An error report file with more information is saved as:
# /opt/hadoop/hs_err_pid646.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#
Aborted (core dumped)

Issue Links

• links to: GitHub Pull Request #1317