[jira] [Commented] (STREAMS-358) Refreshing indexes in EsPW.cleanUp can result in streams not terminating

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STREAMS-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14720511#comment-14720511 ] 

ASF GitHub Bot commented on STREAMS-358:
----------------------------------------

GitHub user steveblackmon opened a pull request:

    https://github.com/apache/incubator-streams/pull/252

    resolves STREAMS-358

    now you have to explicitly ask for a refresh for a refresh to occur 

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

    $ git pull https://github.com/apache/incubator-streams STREAMS-358

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

    https://github.com/apache/incubator-streams/pull/252.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 #252
    
----
commit 193151fb631052a1d589b6122d62627b1c6f49cb
Author: Steve Blackmon (@steveblackmon) <sb...@apache.org>
Date:   2015-08-28T20:14:39Z

    resolves STREAMS-358
    now you have to explicitly ask for a refresh for a refresh to occur

----


> Refreshing indexes in EsPW.cleanUp can result in streams not terminating
> ------------------------------------------------------------------------
>
>                 Key: STREAMS-358
>                 URL: https://issues.apache.org/jira/browse/STREAMS-358
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>
> Refreshing indexes in EsPW cleanup can result in streams not terminating, because refreshing often takes longer than the local runtime tolerance for components to terminate.
> Make refresh an option in EsPWConf and default to false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)