| 2022-05-31
      
      § | 
    
  | 18:48 | <ottomata> | sudo -u hdfs hdfs dfsadmin -safemode leave on an-master1001 | [analytics] | 
            
  | 18:12 | <ottomata> | sudo service hadoop-hdfs-namenode start on an-master1002 | [analytics] | 
            
  | 18:10 | <ottomata> | sudo -u hdfs hdfs dfsadmin -safemode enter | [analytics] | 
            
  | 17:47 | <btullis> | starting namenode services on am-master1001 | [analytics] | 
            
  | 17:44 | <btullis> | restarting the datanodes on all five of the affected hadoop workers. | [analytics] | 
            
  | 17:43 | <btullis> | restarting journalnode service on each of the five hadoop workers with journals. | [analytics] | 
            
  | 17:41 | <btullis> | resizing each journalnode with resize2fs | [analytics] | 
            
  | 17:38 | <btullis> | sudo lvresize -L+20G analytics1069-vg/journalnode | [analytics] | 
            
  | 17:38 | <btullis> | increasing each of the hadoop journalnodes by 20 GB | [analytics] | 
            
  | 17:33 | <ottomata> | stop journalnodes and datanodes on 5 hadoop journalnode hosts | [analytics] | 
            
  | 17:30 | <btullis> | stopped the hdfs-namenode service on an-master100[1-2] | [analytics] | 
            
  | 15:36 | <milimetric> | dropped razzi databases and deleted HDFS directories (in trash) | [analytics] | 
            
  | 06:26 | <elukey> | `elukey@an-master1001:~$ sudo systemctl reset-failed hadoop-clean-fairscheduler-event-logs.service` | [analytics] |