TensorBoard can’t find your event files.Log directory: hdfs://tensorboard_log

Open
#6,872 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
hadoop, python

Research direction

Start at io_wrapper.GetLogdirSubdirectories and the tf.io.gfile.exists call shown in the traceback, then investigate why HadoopFileSystem is not initialized for hdfs://tensorboard_log. Reproduce with the reported TensorBoard 2.11.2 setup; done means an HDFS log directory can be loaded without the InternalError.

Written by the indexing model from the issue text.

Description

TensorBoard 2.11.2 at http://wedata3:6006/ (Press CTRL+C to quit)
Exception in thread Reloader:
Traceback (most recent call last):
File "/opt/python/lib/python3.7/threading.py", line 926, in _bootstrap_inner
self.run()
File "/opt/python/lib/python3.7/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/opt/python/lib/python3.7/site-packages/tensorboard/backend/event_processing/data_ingester.py", line 104, in _reload
self._multiplexer.AddRunsFromDirectory(path, name)
File "/opt/python/lib/python3.7/site-packages/tensorboard/backend/event_processing/plugin_event_multiplexer.py", line 204, in AddRunsFromDirectory
for subdir in io_wrapper.GetLogdirSubdirectories(path):
File "/opt/python/lib/python3.7/site-packages/tensorboard/backend/event_processing/io_wrapper.py", line 195, in GetLogdirSubdirectories
if not tf.io.gfile.exists(path):
File "/opt/python/lib/python3.7/site-packages/tensorflow/python/lib/io/file_io.py", line 290, in file_exists_v2
_pywrap_file_io.FileExists(compat.path_to_bytes(path))
tensorflow.python.framework.errors_impl.InternalError: HadoopFileSystem is not initialized correctly

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

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.

More from tensorflow/tensorboard

All issues in tensorflow/tensorboard

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.