You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2011/01/28 10:22:43 UTC

[jira] Created: (WHIRR-223) [HBase] Running hbase-master and hbase-restserver on same instance does not start master

[HBase] Running hbase-master and hbase-restserver on same instance does not start master
----------------------------------------------------------------------------------------

                 Key: WHIRR-223
                 URL: https://issues.apache.org/jira/browse/WHIRR-223
             Project: Whirr
          Issue Type: Bug
    Affects Versions: 0.3.0
            Reporter: Lars George
            Assignee: Lars George
             Fix For: 0.4.0


There is an issue when the two are assumed to run on the same instance. I checked the whirr.log and it is calling the post-configure once per role. For starters rewriting an existing config is bad, so the post-configure should check before creating dirs or writing config files out. Not sure if that is why the master failed to start but this is not good in any event. While it was called for each I cannot find any output on the server but for the init runscript, maybe I have to enable something to get that output?

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

[jira] Commented: (WHIRR-223) [HBase] Running hbase-master and hbase-restserver on same instance does not start master

Posted by "Lars George (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992921#comment-12992921 ] 

Lars George commented on WHIRR-223:
-----------------------------------

I think this also applies to other services combined. I had a chat on ML where ZK was located with the Master on the same instance and the Master did not start. 

> [HBase] Running hbase-master and hbase-restserver on same instance does not start master
> ----------------------------------------------------------------------------------------
>
>                 Key: WHIRR-223
>                 URL: https://issues.apache.org/jira/browse/WHIRR-223
>             Project: Whirr
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>            Reporter: Lars George
>            Assignee: Lars George
>             Fix For: 0.4.0
>
>
> There is an issue when the two are assumed to run on the same instance. I checked the whirr.log and it is calling the post-configure once per role. For starters rewriting an existing config is bad, so the post-configure should check before creating dirs or writing config files out. Not sure if that is why the master failed to start but this is not good in any event. While it was called for each I cannot find any output on the server but for the init runscript, maybe I have to enable something to get that output?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (WHIRR-223) [HBase] Running hbase-master and hbase-restserver on same instance does not start master

Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WHIRR-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrei Savu updated WHIRR-223:
------------------------------

    Fix Version/s:     (was: 0.4.0)

> [HBase] Running hbase-master and hbase-restserver on same instance does not start master
> ----------------------------------------------------------------------------------------
>
>                 Key: WHIRR-223
>                 URL: https://issues.apache.org/jira/browse/WHIRR-223
>             Project: Whirr
>          Issue Type: Bug
>    Affects Versions: 0.3.0
>            Reporter: Lars George
>            Assignee: Lars George
>
> There is an issue when the two are assumed to run on the same instance. I checked the whirr.log and it is calling the post-configure once per role. For starters rewriting an existing config is bad, so the post-configure should check before creating dirs or writing config files out. Not sure if that is why the master failed to start but this is not good in any event. While it was called for each I cannot find any output on the server but for the init runscript, maybe I have to enable something to get that output?

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira