flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zentol <...@git.apache.org>
Subject [GitHub] flink issue #2974: [FLINK-5298] TM checks that log file exists
Date Fri, 09 Dec 2016 21:04:03 GMT
Github user zentol commented on the issue:

    https://github.com/apache/flink/pull/2974
  
    It should display "Fetching TaskManager log failed.", and log the exception. (see `TaskManagerLogHandler#respondAsLeader():
logPathFuture.exceptionally(...))
    
    This isn't a case that can only happen on Mesos. If the log was is deleted while the TM
is running we have the exact same problem, except in this case it is in fact an error and
should be displayed as such. Same if the logging is broken.
    
    I agree that we should display something different if we know that no log file should
exist; how/whether we can find that out however i simply don't know. That's maybe something
that you could weigh in.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message