Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.13.0
-
None
-
None
Description
When I start a task and go to the task logs, nothing shows up for a while. An examination of TaskLog.Writer and TaskLog.Reader reveals:
1. The TaskLog.Reader relies on the presence of a split.idx to identify the parts of the logs to display.
2. The TaskLog.Writer only updates the split.idx file when it moves on to the next log.
As a result, updates to the log only get pushed when an entire file is done.
Why is there a split.idx file? It seems that since files are called part-00000, part-00001, etc., the TaskLog.Reader can just look at all files and arrange them by alphabetical order. The split.idx file also contains file length, but this data is already stored by the filesystem.
If nobody has objections, I'd like to write a patch to eliminate the split.idx file.