Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
From: aljoscha <git@git.apache.org>
To: issues@flink.incubator.apache.org
Reply-To: issues@flink.incubator.apache.org
Message-ID: <git-pr-1686-flink@git.apache.org>
Subject: [GitHub] flink pull request: [FLINK-3450] Duplicate TypeSerializer in
 State...
Content-Type: text/plain
Date: Mon, 22 Feb 2016 09:48:31 +0000 (UTC)

GitHub user aljoscha opened a pull request:

    https://github.com/apache/flink/pull/1686

    [FLINK-3450] Duplicate TypeSerializer in StateDescriptor.writeObject

    The StateDescriptor can be serializer asynchronously in case of
    asynchronous checkpoints. In that case two threads would try to
    concurrently use the TypeSerializer: The normal state updating and the
    checkpoint serialization. If the TypeSerializer is a KryoSerializer this
    can lead to problems. Therefore the need to duplicate it before using in
    "writeObject".

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

    $ git pull https://github.com/aljoscha/flink state-descriptor-kryo-fix

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

    https://github.com/apache/flink/pull/1686.patch

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

    This closes #1686
    
----
commit 51d8dc9fa5cdd84b6cc1c7711af96ddabf12aaf6
Author: Aljoscha Krettek <aljoscha.krettek@gmail.com>
Date:   2016-02-19T14:38:57Z

    [FLINK-3450] Duplicate TypeSerializer in StateDescriptor.writeObject
    
    The StateDescriptor can be serializer asynchronously in case of
    asynchronous checkpoints. In that case two threads would try to
    concurrently use the TypeSerializer: The normal state updating and the
    checkpoint serialization. If the TypeSerializer is a KryoSerializer this
    can lead to problems. Therefore the need to duplicate it before using in
    "writeObject".

----


---
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.
---