[
https://issues.apache.org/jira/browse/ACCUMULO-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15135683#comment-15135683
]
Christopher Tubbs commented on ACCUMULO-4136:
---------------------------------------------
I'm not too familiar with docker. Where is the accumulo configuration being set
up? Normally, I'd recommend somebody run {{bin/bootstrap_config.sh}} and
{{bin/build_native_library.sh}}, and then review {{conf/*}} before running
{{bin/accumulo init}}, if the user were launching from the unmodified upstream
tarball. But, perhaps those are already set up in a previous step? Otherwise,
there won't be a {{conf/masters}} and {{conf/monitor}} file containing a
hostname at all.
I certainly don't think we want to modify the scripts to assume a {{$HOSTNAME}}
variable is set in the user's environment, and that's the location they want to
run the monitor, because that may not be the case.
I will say that the {{bin/start-all.sh}}, class of scripts are really designed
specifically for a cluster environment from an unpacked tarball. It could work
for a docker container, but it might be better for it to do something simpler
and more appropriate for that particular kind of environment (just like the
accumulo RPMs in Fedora use systemd units instead of these scripts to launch).
But again, I'm not that familiar with docker, so... I'm not sure what would be
better.
> 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)
