[
https://issues.apache.org/jira/browse/STORM-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Whittemore updated STORM-1889:
------------------------------------
Description: (was: I run the Storm using the following
docker-compose.yml
{code}
version: '2'
services:
zookeeper:
image: jplock/zookeeper:3.4.8
restart: always
nimbus:
image: 31z4/storm:1.0.0
command: nimbus -c storm.log.dir="/logs" -c
storm.zookeeper.servers="[\"zookeeper\"]" -c nimbus.host="nimbus"
depends_on:
- zookeeper
restart: always
ports:
- 6627:6627
volumes:
- logs:/logs
supervisor:
image: 31z4/storm:1.0.0
command: supervisor -c storm.log.dir="/logs" -c
storm.zookeeper.servers="[\"zookeeper\"]" -c nimbus.host="nimbus"
depends_on:
- nimbus
restart: always
volumes:
- logs:/logs
logviewer:
image: 31z4/storm:1.0.0
command: logviewer -c storm.log.dir="/logs"
restart: always
ports:
- 8000:8000
volumes:
- logs:/logs
ui:
image: 31z4/storm:1.0.0
command: ui -c storm.log.dir="/logs" -c nimbus.host="nimbus"
depends_on:
- nimbus
- logviewer
restart: always
ports:
- 8080:8080
volumes:
- logs:/log
volumes:
logs: {}
{code}
And opening the logs from the Storm UI doesn't work because all links are
pointing to different container ids as hosts.
I guess adding an ability to explicitly specify the logviewer host in the
storm.yaml would solve the issue.)
> Datatables error message displayed when viewing UI
> --------------------------------------------------
>
> Key: STORM-1889
> URL: https://issues.apache.org/jira/browse/STORM-1889
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-ui
> Affects Versions: 1.0.1
> Reporter: Simon Whittemore
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
