flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From uce <...@git.apache.org>
Subject [GitHub] flink pull request: [FLINK-3595] [runtime] Eagerly destroy buffer ...
Date Fri, 11 Mar 2016 18:34:51 GMT
Github user uce commented on the pull request:

    Regarding the stack trace of the Kafka test: the log shows two failures.
    - The stack trace you posted is part of a test time out (that's why you have the interruption
of the client in your stack trace), and
    - a job restart when not enough task managers are connected (NoResourceAvailableException).
    Looking at the code, the failures seem unrelated. Do you think that's not the case?

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.

View raw message