In starting spark shell –master yarn, we will find an error when spark shell is started
YarnClientSchedulerBackend: Yarn application has already exited with state FAILED
At this point we visit the yarn process to see the history of the start-up time error exception: ERRORorg.apache.hadoop.hdfs.server.namenode.NameNode: RECEIVED SIGNAL 15: SIGTERM (as shown), the general access to the port number is http://Localhost_name+8088 (default)
Solution:
This problem often occurs when the jdk version is 1.8. You can directly modify the configuration of yarn-site.xml in hadoop and distribute it to each cluster, and restart the cluster.
<property>
<name>yarn.nodemanager.vmem-pmem-ratio</name>
<value>10</value>
</property>
<property>
<name>yarn.nodemanager.vmem-check-enabled</name>
<value>false</value>
</property>Read More:
- [Solved] Linux Service Start Error: *.service: Main process exited, code=exited, status=203/EXEC
- [Solved] ioctl_cfg80211.c:1141:45: error: ‘struct wireless_dev’ has no member named ‘sme_state’
- Nginx Startup Error: Job for nginx.service failed because the control process exited with error code
- [Solved] Job for network.service failed because the control process exited with error code. See “systemctl st
- [Solved] FTP Setup Error: Job for vsftpd.service failed because the control process exited with error code…
- [Solved] Job for docker.service failed because the control process exited with error code. After changing the docker configuration
- [Solved] mongo Startup Error: ERROR: child process failed, exited with error number 1
- [Solved] ERROR: Linux route delete command failed: external program exited with error status: 2
- Virtual machine failed to start network service error: ob for network.service failed because the control process exited with error code
- [Solved] docker Startup Error: Job for docker.service failed because the control process exited with error code
- [Solved] Docker Staratup Error: Failed to start Docker Application Container Engineadsafdsad.
- Failed to Connect NVIDIA Driver: NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver
- [Solved] An unexpected error has occurred. Conda has prepared the above report.
- [Solved] NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver
- [Solved] NVIDIA-SMI has failed because it couldn‘t communicate with the NVIDIA driver.
- [Solved] svn: OPTIONS of ‘https://xxx/svn/xxx’: SSL handshake failed: SSL error: Key usage violation in certificate has been detected.
- [Solved] docker Error: System has not been booted with systemd as init system (PID 1). Can‘t operate. Failed to con
- Ffmpeg about Avio_alloc_Context application for memory release
- Apache Cannot Start: SSL Library Error: -8181 Certificate has expired
- [Solved] SSH WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!