You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2014/09/16 13:15:34 UTC
[jira] [Updated] (LUCENE-5948) Improve RateLimiters Initialization
semantics
[ https://issues.apache.org/jira/browse/LUCENE-5948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Varun Thacker updated LUCENE-5948:
----------------------------------
Attachment: LUCENE-5948.patch
Thanks for looking into it!
Patch which initializes lastNS in the ctor and fixes the test to remove the initial pause. All tests pass
> Improve RateLimiters Initialization semantics
> -----------------------------------------------
>
> Key: LUCENE-5948
> URL: https://issues.apache.org/jira/browse/LUCENE-5948
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Varun Thacker
> Attachments: LUCENE-5948.patch
>
>
> I was working on SOLR-6485 when I realized that the first time pause is called even if we write a lot of bytes pause doesn't work correctly because in SimpleRateLimiter.pause() lastNS is 0 and startNS is always more than targetNS.
> If we remove the following line from TestRateLimiter.testPause() then the test fails -
> {code}
> limiter.pause(2);//init
> {code}
> Should we do one of the following ?
> 1. Initialize lastNS in the ctor {code}lastNS = System.nanoTime();{code}
> 2. Add a method saying start() which does the same
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org