You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "David Holiday (JIRA)" <ji...@apache.org> on 2016/02/04 19:16:39 UTC

[jira] [Created] (ACCUMULO-4136) monitor fails to start when accumulo is running in a docker container when host is set to either localhost or 0.0.0.0

David Holiday created ACCUMULO-4136:
---------------------------------------

             Summary: monitor fails to start when accumulo is running in a docker container when host is set to either localhost or 0.0.0.0
                 Key: ACCUMULO-4136
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4136
             Project: Accumulo
          Issue Type: Bug
         Environment: accumulo 1.7.0
Docker version 1.7.1, build 786b29d
docker image ubuntu 14.04
            Reporter: David Holiday
            Priority: Minor


when running accumulo inside a docker container, the accumulo monitor service won't start unless line 61 of ../accumulo-1.7.0/bin/start-all.sh is changed from

    ${bin}/start-server.sh $MONITOR monitor

    to

    ${bin}/start-server.sh $HOSTNAME monitor

or specifying $HOSTNAME in the ../accumulo-1.7.9/conf/monitor file. Enabling variable ACCUMULO_MONITOR_BIND_ALL has no effect. The only way to bring the monitor service up is to use the hostname explicitly. 

here is a working accumulo/zookeeper/hadoop stack that's been dockerized. commenting out line 58 of  ../dockerized_accumulo/accumulo/Dockerfile before provisioning the containers will demonstrate the problem.

https://github.com/davidholiday/dockerized_accumulo



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)