@Bhushan kumar In the terminal where you are running the Hadoop Cline you can set the "HADOOP_OPTS" to add the remote debugging option. Example: # export HADOOP_OPTS = $HADOOP_OPTS -agentlib:jdwp=transport=dt_socket,address=9999,server=y,suspend=n # hdfs dfs -ls / . ... View more

@PeiHe Zhang Following are the two jars where we can find this class "org.apache.hadoop.yarn.client.RequestHedgingRMFailoverProxyProvider" in HDP 2.6 installation. Please make sure that these jars are added to the classpath. /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-common-2.7.3.2.6.1.0-129.jar /usr/hdp/current/hadoop-yarn-client/hadoop-yarn-common.jar . Typically the classpath setting can be found in Ambari UI --> Yarn --> Configs --> Advanced --> "Advanced yarn-site" as following, so please check if that path is correct at your end. (Following is the default value that we usually get) yarn.application.classpath = /etc/hadoop/conf,/usr/hdp/current/hadoop-client/*,/usr/hdp/current/hadoop-client/lib/*,/usr/hdp/current/hadoop-hdfs-client/*,/usr/hdp/current/hadoop-hdfs-client/lib/*,/usr/hdp/current/hadoop-yarn-client/*,/usr/hdp/current/hadoop-yarn-client/lib/* . ... View more

@Chiranjeevi Nimmala Good to hear that your issue is resolved. It will be also wonderful if you can mark this thread as "Answered" (Accepted) so that it will be useful for other HCC users to quickly browse the correct answer for their issues. ... View more

@Chiranjeevi Nimmala It looks somewhere similar to : https://issues.apache.org/jira/browse/HDFS-12029 (although it is for DataNode) But looks like the issue is "jsvc" is crashing due to less "Xss" (Stack Size Value) So please try increasing the stack size to a higher value like "-Xss2m" inside the file "/usr/hdp/2.6.0.3-8/hadoop-hdfs/bin/hdfs.distro" Example: (Following line should be added to somewhere at the top like above DEFAULT_LIBEXEC_DIR so that following script can utilize this value. export HADOOP_OPTS="$HADOOP_OPTS -Xss2m" DEFAULT_LIBEXEC_DIR="$bin"/../libexec . OR set the -Xss2m inside the following block of the "hadoop.distro" To apply the setting specifically for NFS3, In all the "HADOOP_OPTS" of the following block: # Determine if we're starting a privileged NFS daemon, and if so, redefine appropriate variables if [ "$COMMAND" == "nfs3" ] && [ "$EUID" -eq 0 ] && [ -n "$HADOOP_PRIVILEGED_NFS_USER" ]; then if [ -n "$JSVC_HOME" ]; then if [ -n "$HADOOP_PRIVILEGED_NFS_PID_DIR" ]; then HADOOP_PID_DIR=$HADOOP_PRIVILEGED_NFS_PID_DIR fi if [ -n "$HADOOP_PRIVILEGED_NFS_LOG_DIR" ]; then HADOOP_LOG_DIR=$HADOOP_PRIVILEGED_NFS_LOG_DIR HADOOP_OPTS="$HADOOP_OPTS -Dhadoop.log.dir=$HADOOP_LOG_DIR -Xss2m" fi HADOOP_IDENT_STRING=$HADOOP_PRIVILEGED_NFS_USER HADOOP_OPTS="$HADOOP_OPTS -Dhadoop.id.str=$HADOOP_IDENT_STRING -Xss2m" starting_privileged_nfs="true" else echo "It looks like you're trying to start a privileged NFS server, but"\ "\$JSVC_HOME isn't set. Falling back to starting unprivileged NFS server." fi fi Then restart NFS. Reference RHEL7 kernel issue: https://access.redhat.com/errata/RHBA-2017:1674 . ... View more

@Chiranjeevi Nimmala The following line of error indicates that it's a JVM crash. # An error report file with more information is saved as: # /tmp/hs_err_pid19469.log . So if you can share the complete "/tmp/hs_err_pid19469.log" file here then we can check why the JVM crashed. ... View more