You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2018/12/15 05:42:25 UTC

[GitHub] AlphaGarden opened a new pull request #7312: [FLINK-11169][runtime] fix the problem of not being reloaded for jobmanager's…

AlphaGarden opened a new pull request #7312:  [FLINK-11169][runtime] fix the problem of not being reloaded for jobmanager's…
URL: https://github.com/apache/flink/pull/7312
 
 
   ## What is the purpose of the change
   
   *In the Flink web UI page, we can access the log of jobmanager from the tab under its corresponding page, but we could not reload the log (the content is not up-to-date) since the log file has been cached for 300s in the local client' disk. And this problem occurs because of the incorrect way to check if the file should be cached. *
   
   ## Brief change log
     - *Change the way of checking if the current file is a log file or out flie.*
   
   ## Verifying this change
   
     - *git clone https://github.com/AlphaGarden/flink.git*
     - *cd flink*
     - *git checkout hotfix-web-reload-jobmanager-log*
     - *mvn clean package -DskipTests*
     - *run the ./start-cluster.sh script, then the log for jobmanager should be reloaded from backend evertime we click the refresh button in Flink Web  UI*
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no)
     - The serializers: (no)
     - The runtime per-record code paths (performance sensitive): (yes)
     - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
     - The S3 file system connector: (no)
   
   ## Documentation
     - Does this pull request introduce a new feature? (no)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services