Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
0.10.0, 1.0.0, 0.9.6
-
None
-
None
Description
I run the Storm using the following docker-compose.yml
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: {}
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.
Attachments
Issue Links
- incorporates
-
STORM-1758 Distributed log search doesn't work in dockerized environment
- Closed
- is cloned by
-
STORM-2708 View Logs by single point. With using Docker swarm
- Resolved
- relates to
-
STORM-1342 support multiple logviewers per host for container-isolated worker logs
- Closed