Shulou(Shulou.com)06/02 Report--

1. Software environment RHEL6 role jdk-8u45hadoop-2.8.1.tar.gzsshxx.xx.xx.xx ip address NNhadoop1xx.xx.xx.xx ip address DNhadoop2xx.xx.xx.xx ip address DNhadoop3xx.xx.xx.xx ip address DNhadoop4xx.xx.xx.xx ip address DNhadoop5

The pseudo-distributed deployment involved only requires the host hadoop1

2. Mutual trust of startup keys

HDFS start

[hadoop@hadoop01 hadoop] $. / sbin/start-dfs.sh

Starting namenodes on [hadoop01]

The authenticity of host 'hadoop01 (172.16.18.133)' can't be established.

RSA key fingerprint is 8f:e7:6c:ca:6e:40:78:b8:df:6a:b4:ca:52:c7:01:4b.

Are you sure you want to continue connecting (yes/no)? Yes

Hadoop01: Warning: Permanently added 'hadoop01' (RSA) to the list of known hosts.

Hadoop01: chown: changing ownership of `/ opt/software/hadoop-2.8.1/logs': Operation not permitted

Hadoop01: starting namenode, logging to / opt/software/hadoop-2.8.1/logs/hadoop-hadoop-namenode-hadoop01.out

Hadoop01: / opt/software/hadoop-2.8.1/sbin/hadoop-daemon.sh: line 159:

/ opt/software/hadoop-2.8.1/logs/hadoop-hadoop-namenode-hadoop01.out: Permission denied

Start if there is an interactive input password, do not enter error permission restrictions, this is because we do not configure mutual trust

Pseudo-distributed we need to configure ssh login trust even on the same machine.

Non-root user public key file permissions must be 600th (except root)

Configure ssh password-free login in hadoop user

[hadoop@hadoop01 .ssh] $cat id_rsa.pub > authorized_keys

[hadoop@hadoop01 .ssh] $chmod 600 authorized_keys

[hadoop@hadoop01 hadoop] $ssh hadoop01 date

[hadoop@hadoop01 .ssh] $

[hadoop@hadoop01 hadoop] $. / sbin/start-dfs.sh

Starting namenodes on [hadoop01]

Hadoop01: starting namenode, logging to / opt/software/hadoop-2.8.1/logs/hadoop-hadoop-namenode-hadoop01.out

Hadoop01: starting datanode, logging to / opt/software/hadoop-2.8.1/logs/hadoop-hadoop-datanode-hadoop01.out

Starting secondary namenodes [hadoop01]

Hadoop01: starting secondarynamenode, logging to / opt/software/hadoop-2.8.1/logs/hadoop-hadoop-secondarynamenode-hadoop01.out

[hadoop@hadoop01 hadoop] $jps

1761 Jps

1622 SecondaryNameNode

1388 DataNode

1276 NameNode

3. Process process information unavailable problem

There are two situations: 1. The process does not exist, and process information unavailable

2. Process presence report process information unavailable

For the first case:

[hadoop@hadoop01 sbin] $jps

3108 DataNode

4315 Jps

4156 SecondaryNameNode

2990 NameNode

[hadoop@hadoop01 hsperfdata_hadoop] $ls

5295 5415 5640

[hadoop@hadoop01 hsperfdata_hadoop] $ll

Total 96

-rw- 1 hadoop hadoop 32768 Apr 27 09:35 5295

-rw- 1 hadoop hadoop 32768 Apr 27 09:35 5415

-rw- 1 hadoop hadoop 32768 Apr 27 09:35 5640

[hadoop@hadoop01 hsperfdata_hadoop] $pwd

/ tmp/hsperfdata_hadoop

/ tmp/hsperfdata_hadoop

Record the process number displayed by jps. If jps sees an error at this time,

[hadoop@hadoop01 tmp] $jps

3330 SecondaryNameNode-process information unavailable

3108 DataNode-process information unavailable

3525 Jps

2990 NameNode-process information unavailable

Query whether the exception process exists

[hadoop@hadoop01 tmp] $ps-ef | grep 3330

Hadoop 3845 2776 0 09:29 pts/6 00:00:00 grep 3330

For the process no longer exists, ok goes to / tmp/hsperfdata_xxx to delete the file and restarts the process directly.

Jps queries the current user's hsperfdata_ current user / file

[root@hadoop01 ~] # jps

7153-process information unavailable

8133-process information unavailable

7495-process information unavailable

8489 Jps

[root@hadoop01 ~] # ps-ef | grep 7153-check the existence of abnormal processes

Hadoop 7153 1 2 09:47? 00:00:17 / usr/java/jdk1.8.0_45/bin/java-Dproc_namenode-Xmx1000m-Djava.net.preferIPv4Stack=true-Dhadoop.log.dir=/opt/software/hadoop-2.8.1/logs-Dhadoop.log.file=hadoop.log-Dhadoop.home.dir=/opt/software/hadoop-2.8.1-Dhadoop.id.str=hadoop-Dhadoop.root.logger=INFO Console-Djava.library.path=/opt/software/hadoop-2.8.1/lib/native-Dhadoop.policy.file=hadoop-policy.xml-Djava.net.preferIPv4Stack=true-Dhadoop.log.dir=/opt/software/hadoop-2.8.1/logs-Dhadoop.log.file=hadoop-hadoop-namenode-hadoop01.log-Dhadoop.home.dir=/opt/software/hadoop-2.8.1-Dhadoop.id.str=hadoop-Dhadoop.root.logger=INFO RFA-Djava.library.path=/opt/software/hadoop-2.8.1/lib/native-Dhadoop.policy.file=hadoop-policy.xml-Djava.net.preferIPv4Stack=true-Dhadoop.security.logger=INFO,RFAS-Dhdfs.audit.logger=INFO,NullAppender-Dhadoop.security.logger=INFO,RFAS-Dhdfs.audit.logger=INFO,NullAppender-Dhadoop.security.logger=INFO,RFAS-Dhdfs.audit.logger=INFO,NullAppender-Dhadoop.security.logger=INFO,RFAS org.apache.hadoop.hdfs.server.namenode.NameNode

Root 8505 2752 0 09:58 pts/6 00:00:00 grep 7153

If it exists, the process information unavailable is checked by the current user. At this time, check whether the process exists. The current user ps-ef | grep process number, depending on the user running the process, not switching users.

[hadoop@hadoop01 hadoop] $jps-toggles the hadoop user viewing process

7153 NameNode

8516 Jps

8133 DataNode

7495 SecondaryNameNode

The switching user finds that the process is normal.

This situation is that the user you are viewing is wrong. Hadoop View jps is not running user View. This situation does not require any processing. The service is running normally.

Summary: corresponding to process information unavailable error, processing:

1. Check whether the process exists (process does not exist, delete / tmp/hsperfdata_xxx, restart the process)

two。 If the process exists, check the existing process running user, if not the current user, rerun jps after switching users.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.