tensorflow / tensorflow/tensorboard

Loading data from multiple remote servers in tensorboard

Open
#1,525 1 comment 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
7.2k
Forks
1.7k
Avg merge
4d 22h
Merged PRs (30d)
1

Description

This is more a feature question rather than a bug. I hope others will find it useful too.

I am running tensorboard on a remote server, server_A. I was wondering if I somehow can get tensorboard to also look at the event files stored in the runs directory on a different server, server_B. I have started with the command below:

tensorboard --logdir=path/to/logs/1,server_B:/path/to/logs/2

That did not work so I simplified a bit and tried to get tensorboard to "look" at the event files on the remote alone. I tried the following:

tensorboard --logdir=/path/to/logs/2 --host=112.11.15.72 --port=8888

where the ip in host is the private IP address of server_B, for which I configured an inbound Custom TCP connection on that port. The error I get is:

E1018 11:44:05.649294 MainThread program.py:201] TensorBoard could not bind to unavailable address 112.11.15.72
E1018 11:44:05.649293 140128884926208 program.py:201] TensorBoard could not bind to unavailable address 112.11.15.72
ERROR: TensorBoard could not bind to unavailable address 112.11.15.72

Is it possible to achieve this?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the two command-line examples using tensorboard --logdir and --host, noting the remote-server setup and bind error shown in the issue. Determine whether remote event-file locations are intended to be supported; done means either a documented working approach or a defined implementation path with coverage for the requested behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.