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

Posted to dev@apex.apache.org by vrozov <gi...@git.apache.org> on 2015/10/10 04:19:36 UTC

[GitHub] incubator-apex-core pull request: APEX-184

GitHub user vrozov opened a pull request:

    https://github.com/apache/incubator-apex-core/pull/110

    APEX-184 

    Suspend DataListIterator and release block reference in case LogicalNode is not ready to send data to downstream operator. Do not enable read in resumeReadIfSuspended when not able to switch to a new buffer. Fix possible race condition in Block acquire.
    
    @ilooner please pull and test. @243826, @PramodSSImmaneni please review

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

    $ git pull https://github.com/vrozov/incubator-apex-core APEX-184

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

    https://github.com/apache/incubator-apex-core/pull/110.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 #110
    
----
commit 76a94ce11ff17dc867f8747f1ef622d7ced724f6
Author: Vlad Rozov <v....@datatorrent.com>
Date:   2015-10-10T00:35:30Z

    APEX-184 #resolve Suspend DataListIterator and release block reference in case LogicalNode is not ready to send data to downstream operator. Do not enable read in resumeReadIfSuspended when not able to switch to a new buffer. Fix possible race condition in Block acquire.

----


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

[GitHub] incubator-apex-core pull request: APEX-184

Posted by vrozov <gi...@git.apache.org>.

Github user vrozov commented on the pull request:

    https://github.com/apache/incubator-apex-core/pull/110#issuecomment-148205660
  
    Found an issue with synchronization. Will fix and reopen.


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

[GitHub] incubator-apex-core pull request: APEX-184

Posted by ilooner <gi...@git.apache.org>.

Github user ilooner commented on the pull request:

    https://github.com/apache/incubator-apex-core/pull/110#issuecomment-147459758
  
    @vrozov started test application now. Will observe for the day and let you know if there is an issue.


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

[GitHub] incubator-apex-core pull request: APEX-184

Posted by vrozov <gi...@git.apache.org>.

Github user vrozov closed the pull request at:

    https://github.com/apache/incubator-apex-core/pull/110


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

[GitHub] incubator-apex-core pull request: APEX-184

Posted by PramodSSImmaneni <gi...@git.apache.org>.

Github user PramodSSImmaneni commented on the pull request:

    https://github.com/apache/incubator-apex-core/pull/110#issuecomment-147476945
  
    will do


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