[
https://issues.apache.org/jira/browse/ACCUMULO-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139636#comment-15139636
]
Josh Elser commented on ACCUMULO-4136:
--------------------------------------
bq. the reason I posted this was because it was my understanding specifying
0.0.0.0 in ../conf/monitor and setting ACCUMULO_MONITOR_BIND_ALL should've
worked. as I understand you, expected behavior is for that not to work.
Gotcha. No, for your single docker setup, this should work. When you run
Accumulo on many nodes, specifying 0.0.0.0 will result in the monitor starting
wherever you run start-all.sh from which is undesired. It's not that what you
did shouldn't work, it's just not what we would recommend you do (the fact that
it does work is only because you're on one "node").
bq. tell you what – give me an hour or so to download and setup accumulo
locally and see what happens when I play with these settings outside the
context of docker. I'll post the results and we can go from there with this
ticket. sound good?
No rush whatsoever. We all jump in and out of tickets as time permits :)
> 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)
