We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We encountered this issue while writing tensorboard events into a GCS Fuse mounted directory tree.
It turns out that GCS fuse requires the os buffers to to be flushed before others that also mount the same GCS bucket can see the writes (c.f. https://github.com/googlecloudplatform/gcsfuse/blob/master/docs/semantics.md#readwrites).
Since https://github.com/lanpa/tensorboardX/blob/master/tensorboardX/record_writer.py#L192 only does a python file buffer level flush, one needs to add another line just below that to call os.fsync. Something like this
os.fsync
def flush(self): self._writer.flush() os.fsync(self._writer.fileno())
With this change, gcs fuse mounted directories behaves as you would expect.
torch.utils.tensorboard has the behavior on GCS fuse described here out of the box.
torch.utils.tensorboard
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We encountered this issue while writing tensorboard events into a GCS Fuse mounted directory tree.
It turns out that GCS fuse requires the os buffers to to be flushed before others that also mount the same GCS bucket can see the writes (c.f. https://github.com/googlecloudplatform/gcsfuse/blob/master/docs/semantics.md#readwrites).
Since https://github.com/lanpa/tensorboardX/blob/master/tensorboardX/record_writer.py#L192 only does a python file buffer level flush, one needs to add another line just below that to call
os.fsync
. Something like thisWith this change, gcs fuse mounted directories behaves as you would expect.
torch.utils.tensorboard
has the behavior on GCS fuse described here out of the box.The text was updated successfully, but these errors were encountered: