You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Prateek Maheshwari (JIRA)" <ji...@apache.org> on 2019/01/22 22:01:00 UTC

[jira] [Created] (SAMZA-2082) Do not block the run loop if a new commit is requested when the last commit is in progress

Prateek Maheshwari created SAMZA-2082:
-----------------------------------------

             Summary: Do not block the run loop if a new commit is requested when the last commit is in progress
                 Key: SAMZA-2082
                 URL: https://issues.apache.org/jira/browse/SAMZA-2082
             Project: Samza
          Issue Type: Improvement
            Reporter: Prateek Maheshwari
            Assignee: Prateek Maheshwari


With the async commit feature, task commit() does not block task process()/processAsync() invocation. However, if another commit is then requested while the first hasn't completed (i.e., it took longer than task.commit.ms), it blocks the run loop.

Long commits can be useful when performing long running background operations. E.g., backing up local state to a durable file system.

This task is to prevent a second commit from blocking the run loop. This may require a new configuration for "max commit duration", which is the maximum amount of time a commit is allows to take. This is similar task.callback.timeout.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)