Index: src/docbkx/troubleshooting.xml =================================================================== --- src/docbkx/troubleshooting.xml (revision 1097898) +++ src/docbkx/troubleshooting.xml (working copy) @@ -28,7 +28,7 @@ RegionServer suicides are “normal�, as this is what they do when something goes wrong. For example, if ulimit and xcievers (the two most important initial settings, see ) - aren’t changed, it will make it impossible at some point for datanodes to create new threads + aren’t changed, it will make it impossible at some point for DataNodes to create new threads that from the HBase point of view is seen as if HDFS was gone. Think about what would happen if your MySQL database was suddenly unable to access files on your local file system, well it’s the same with HBase and HDFS. Another very common reason to see RegionServers committing seppuku is when they enter @@ -145,7 +145,7 @@ Child, its MapReduce task, cannot tell which type exactly Hadoop TaskTracker, manages the local Childs Hadoop DataNode, serves blocks - HQuorumPeer, a zookeeper ensemble member + HQuorumPeer, a ZooKeeper ensemble member Jps, well… it’s the current process ThriftServer, it’s a special one will be running only if thrift was started jmx, this is a local process that’s part of our monitoring platform ( poorly named maybe). You probably don’t have that. @@ -275,7 +275,7 @@ - And here is a master trying to recover a lease after a region server died: + And here is a master trying to recover a lease after a RegionServer died: "LeaseChecker" daemon prio=10 tid=0x00000000407ef800 nid=0x76cd waiting on condition [0x00007f6d0eae2000..0x00007f6d0eae2a70] -- @@ -370,7 +370,7 @@
- System instability, and the presence of "java.lang.OutOfMemoryError: unable to create new native thread in exceptions" HDFS datanode logs or that of any system daemon + System instability, and the presence of "java.lang.OutOfMemoryError: unable to create new native thread in exceptions" HDFS DataNode logs or that of any system daemon See the Getting Started section on ulimit and nproc configuration.