[ 
https://issues.apache.org/jira/browse/HBASE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581191#action_12581191
 ] 

Jim Kellerman commented on HBASE-537:
-------------------------------------

? It is outside the loop:
{code}
      String message = "Waiting for dfs to exit safe mode...";
      while (((DistributedFileSystem) fs).setSafeMode(
          FSConstants.SafeModeAction.SAFEMODE_GET)) {
        System.out.println(message);
        LOG.info(message);
...
{code}

> We no longer wait on hdfs to exit safe mode
> -------------------------------------------
>
>                 Key: HBASE-537
>                 URL: https://issues.apache.org/jira/browse/HBASE-537
>             Project: Hadoop HBase
>          Issue Type: Bug
>    Affects Versions: 0.1.0
>            Reporter: stack
>            Assignee: Jim Kellerman
>            Priority: Blocker
>             Fix For: 0.1.0
>
>         Attachments: patch.txt
>
>
> We used wait on hdfs to exit safe mode before going on to startup hbase but 
> this feature is broken since we moved out of hadoop contrib.  Now when you 
> try start with hdfs in safe mode you get:
> {code}
> 08/03/21 04:39:56 FATAL hbase.HMaster: Not starting HMaster because:
> org.apache.hadoop.ipc.RemoteException: 
> org.apache.hadoop.dfs.SafeModeException: Cannot create directory /hbase010. 
> Name node is in safe mode.
> Safe mode will be turned off automatically.
>         at 
> org.apache.hadoop.dfs.FSNamesystem.mkdirsInternal(FSNamesystem.java:1571)
>         at org.apache.hadoop.dfs.FSNamesystem.mkdirs(FSNamesystem.java:1559)
>         at org.apache.hadoop.dfs.NameNode.mkdirs(NameNode.java:422)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> {code}
> If you are lucky, it appears on STDOUT/ERR but may just be stuffed into logs 
> and all looks like its running properly.
> Noticed first by Lars George.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to