[
https://issues.apache.org/jira/browse/ACCUMULO-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeffrey Manno resolved ACCUMULO-4136.
-------------------------------------
Resolution: Not A Problem
I confirm that the monitor properly starts in accumulo 2.x when trying to start
with 0.0.0.0. That, along with the age of the ticket and the appropriate
solutions and alternatives already given in the comments, is enough reason to
close this ticket. If this problem still occurs, please feel free to create a
new issue or PR at https://github.com/apache/accumulo.
> 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
(v8.3.4#803005)
