web-dev-qa-db-fra.com

Ubuntu 16.04 tue la session lorsque l'utilisation des ressources est extrêmement élevée

Je travaille sur le projet dans hadoop sur mon ordinateur. Lorsque je commence à utiliser certaines tâches, qui consomment la plupart des ressources disponibles (100% de l'UCT, RAM utilisation élevée), "quelque chose" tue la session de l'utilisateur et tous ses processus.

syslog:

Jun  8 21:38:46 michalo-desktop systemd[1]: Created slice User Slice of hadoop.
Jun  8 21:38:46 michalo-desktop systemd[1]: Starting User Manager for UID 1001...
Jun  8 21:38:46 michalo-desktop systemd[1]: Started Session 21 of user hadoop.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Reached target Paths.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Reached target Sockets.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Reached target Timers.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Reached target Basic System.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Reached target Default.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Startup finished in 126ms.
Jun  8 21:38:46 michalo-desktop systemd[1]: Started User Manager for UID 1001.
Jun  8 21:38:46 michalo-desktop systemd[1]: Stopping User Manager for UID 1001...
Jun  8 21:38:46 michalo-desktop systemd[11932]: Stopped target Default.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Stopped target Basic System.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Stopped target Timers.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Stopped target Sockets.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Reached target Shutdown.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Starting Exit the Session...
Jun  8 21:38:46 michalo-desktop systemd[11932]: Stopped target Paths.
Jun  8 21:38:46 michalo-desktop systemd[11932]: Received SIGRTMIN+24 from PID 12000 (kill).
Jun  8 21:38:46 michalo-desktop systemd[1]: Stopped User Manager for UID 1001.
Jun  8 21:38:46 michalo-desktop systemd[1]: Removed slice User Slice of hadoop.

Le journal ne contient aucune information sur le kill reson. kern.log n'a rien d'intéressant.

16.04performancesystemdhadoopkill
4
michalo2882

C’est Hadoop lui-même qui essaie de supprimer certains de ses processus afin de réduire l’utilisation des ressources sur la machine, mais à la place, il supprime tous les processus qu’il peut en raison d’un bug dans la commande kill .

1
Zoltan