Re: Default value for cooldownMillis in StatsAwareStatelessPartitioner

I tried 30 sec which worked well. ~ Yogi On 18 August 2016 at 22:28, Munagala Ramanath wrote: > Just out of curiosity what is the smallest value that fixes the issue ? > > Ram > > On Thu, Aug 18, 2016 at 3:55 AM, Yogi Devendra > wrote: > > > Hi,

[jira] [Issue Comment Deleted] (APEXCORE-507) Expose firstWindowMillis (the timestamp when the first window is generated) in the API

[ https://issues.apache.org/jira/browse/APEXCORE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gaurav gupta updated APEXCORE-507: -- Comment: was deleted (was: [~davidyan]: Is it not same as startedTime returned as part of

[jira] [Commented] (APEXCORE-507) Expose firstWindowMillis (the timestamp when the first window is generated) in the API

[ https://issues.apache.org/jira/browse/APEXCORE-507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427296#comment-15427296 ] gaurav gupta commented on APEXCORE-507: --- [~davidyan]: Is it not same as startedTime returned as

[jira] [Updated] (APEXMALHAR-2190) Use shared memory to serial spillable data structure

[ https://issues.apache.org/jira/browse/APEXMALHAR-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bright chen updated APEXMALHAR-2190: Description: Spillable Data Structure created lots of temporary memory to serial data

[GitHub] apex-malhar pull request #375: Apexmalhar-2190 shared memory for serialize -...

GitHub user brightchen opened a pull request: https://github.com/apache/apex-malhar/pull/375 Apexmalhar-2190 shared memory for serialize - review only You can merge this pull request into a Git repository by running: $ git pull https://github.com/brightchen/apex-malhar

[jira] [Commented] (APEXMALHAR-2028) Add System.err to ConsoleOutputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427110#comment-15427110 ] ASF GitHub Bot commented on APEXMALHAR-2028: Github user siyuanh closed the pull request

[jira] [Commented] (APEXMALHAR-2028) Add System.err to ConsoleOutputOperator

[ https://issues.apache.org/jira/browse/APEXMALHAR-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427111#comment-15427111 ] ASF GitHub Bot commented on APEXMALHAR-2028: GitHub user siyuanh reopened a pull request:

[GitHub] apex-malhar pull request #365: APEXMALHAR-2028 #resolve #comment add stderr ...

GitHub user siyuanh reopened a pull request: https://github.com/apache/apex-malhar/pull/365 APEXMALHAR-2028 #resolve #comment add stderr for ConsoleOperator Add stderr to ConsleOutputOperator You can merge this pull request into a Git repository by running: $ git pull

[GitHub] apex-malhar pull request #365: APEXMALHAR-2028 #resolve #comment add stderr ...

Github user siyuanh closed the pull request at: https://github.com/apache/apex-malhar/pull/365 --- 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

[jira] [Commented] (APEXMALHAR-2182) benchmark for spillable data structure and storage

[ https://issues.apache.org/jira/browse/APEXMALHAR-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427103#comment-15427103 ] ASF GitHub Bot commented on APEXMALHAR-2182: Github user brightchen closed the pull

[GitHub] apex-malhar pull request #370: APEXMALHAR-2182 #resolve #comment benchmark f...

Github user brightchen closed the pull request at: https://github.com/apache/apex-malhar/pull/370 --- 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

[jira] [Updated] (APEXMALHAR-2168) The setter method for double field is not generated correctly in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2168: --- Summary: The setter method for double field is not generated correctly in

[jira] [Updated] (APEXMALHAR-2168) The in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siyuan Hua updated APEXMALHAR-2168: --- Summary: The in JdbcPOJOInputOperator. (was: Bug Found in JdbcPOJOInputOperator.) >

[jira] [Commented] (APEXMALHAR-2168) Bug Found in JdbcPOJOInputOperator.

[ https://issues.apache.org/jira/browse/APEXMALHAR-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427067#comment-15427067 ] David Yan commented on APEXMALHAR-2168: --- [~siyuan] or [~lushun...@gmail.com]: Please change the

[jira] [Updated] (APEXMALHAR-2197) TimeBasedPriorityQueue.removeLRU throws NoSuchElementException

[ https://issues.apache.org/jira/browse/APEXMALHAR-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] bright chen updated APEXMALHAR-2197: Description: When there are lots of keys and large throughput, the following exception

[jira] [Commented] (APEXCORE-510) Enforce DefaultOutputPort.emit() or Sink.put() thread affinity

[ https://issues.apache.org/jira/browse/APEXCORE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426932#comment-15426932 ] Vlad Rozov commented on APEXCORE-510: - - Changing emit() to be final breaks backward compatibility.

Re: Default value for cooldownMillis in StatsAwareStatelessPartitioner

Just out of curiosity what is the smallest value that fixes the issue ? Ram On Thu, Aug 18, 2016 at 3:55 AM, Yogi Devendra wrote: > Hi, > > Current default value is 2000 ms. > > I tried an application which uses default value. It was noticed that it > leads to

[jira] [Commented] (APEXMALHAR-2197) TimeBasedPriorityQueue.removeLRU throws NoSuchElementException

[ https://issues.apache.org/jira/browse/APEXMALHAR-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426793#comment-15426793 ] ASF GitHub Bot commented on APEXMALHAR-2197: GitHub user brightchen opened a pull

[jira] [Resolved] (APEXCORE-502) Unnecessary byte array copy in DefaultKryoStreamCodec.toByteArray

[ https://issues.apache.org/jira/browse/APEXCORE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Weise resolved APEXCORE-502. --- Resolution: Fixed Fix Version/s: 3.5.0 > Unnecessary byte array copy in

[jira] [Commented] (APEXCORE-502) Unnecessary byte array copy in DefaultKryoStreamCodec.toByteArray

[ https://issues.apache.org/jira/browse/APEXCORE-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426719#comment-15426719 ] ASF GitHub Bot commented on APEXCORE-502: - Github user asfgit closed the pull request at:

[GitHub] apex-core pull request #370: APEXCORE-502 Unnecessary byte array copy in Def...

Github user asfgit closed the pull request at: https://github.com/apache/apex-core/pull/370 --- 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

[jira] [Commented] (APEXMALHAR-2154) Update kafka 0.9 input operator to use new CheckpointNotificationListener

[ https://issues.apache.org/jira/browse/APEXMALHAR-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426497#comment-15426497 ] ASF GitHub Bot commented on APEXMALHAR-2154: GitHub user chaithu14 opened a pull request:

[GitHub] apex-malhar pull request #373: APEXMALHAR-2154 Update the Kafka Input Operat...

GitHub user chaithu14 opened a pull request: https://github.com/apache/apex-malhar/pull/373 APEXMALHAR-2154 Update the Kafka Input Operator to use CheckpointNotificationListener You can merge this pull request into a Git repository by running: $ git pull

Default value for cooldownMillis in StatsAwareStatelessPartitioner

Hi, Current default value is 2000 ms. I tried an application which uses default value. It was noticed that it leads to continuous re-deployment of the operator. Reason could be because 2000 ms is not sufficient for re-deploy+reaching some steady state. How about changing default to 30 sec or 1

[jira] [Commented] (APEXMALHAR-2100) Development of Inner Join Operator using Spillable Datastructures

[ https://issues.apache.org/jira/browse/APEXMALHAR-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426090#comment-15426090 ] ASF GitHub Bot commented on APEXMALHAR-2100: GitHub user chaithu14 reopened a pull

[jira] [Commented] (APEXMALHAR-2100) Development of Inner Join Operator using Spillable Datastructures

[ https://issues.apache.org/jira/browse/APEXMALHAR-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426088#comment-15426088 ] ASF GitHub Bot commented on APEXMALHAR-2100: Github user chaithu14 closed the pull

[GitHub] apex-malhar pull request #330: APEXMALHAR-2100 Implementation of Inner Join ...

GitHub user chaithu14 reopened a pull request: https://github.com/apache/apex-malhar/pull/330 APEXMALHAR-2100 Implementation of Inner Join operator You can merge this pull request into a Git repository by running: $ git pull https://github.com/chaithu14/incubator-apex-malhar

[jira] [Commented] (APEXMALHAR-2195) LineReaderContext gives incorrect results for files not ending with the newline

[ https://issues.apache.org/jira/browse/APEXMALHAR-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15426007#comment-15426007 ] ASF GitHub Bot commented on APEXMALHAR-2195: Github user yogidevendra closed the pull

[jira] [Resolved] (APEXMALHAR-2158) Duplication of data emitted when the Kafka Input Operator(0.8 version) redeploys

[ https://issues.apache.org/jira/browse/APEXMALHAR-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaitanya resolved APEXMALHAR-2158. --- Resolution: Fixed > Duplication of data emitted when the Kafka Input Operator(0.8