beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1392) DoFn teardown not called on empty partitions
Date Sun, 05 Feb 2017 09:29:41 GMT


ASF GitHub Bot commented on BEAM-1392:

GitHub user aviemzur opened a pull request:

    [BEAM-1392] DoFn teardown not called on empty partitions

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull invoke-teardown-on-empty-partition

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1920
commit cf1ea054cedf29ef3bb804410eb56f17f8ff1b37
Author: Aviem Zur <>
Date:   2017-02-05T09:22:00Z

    [BEAM-1392] DoFn teardown not called on empty partitions


> DoFn teardown not called on empty partitions
> --------------------------------------------
>                 Key: BEAM-1392
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Aviem Zur
>            Assignee: Aviem Zur
> DoFn teardown is not called on empty partitions.
> Discovered in a long running Kafka pipeline (read from Kafka -> write to Kafka) where
some partitions did not have data and Kafka producers where being created but not closed,
eventually resulting in {{Too many open files}} exception.

This message was sent by Atlassian JIRA

View raw message