Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1832
Let's back to actual usage of Timer.
```
if (!consumerAutoCommitMode) { // If it is auto commit, no need
to commit offsets manually
commitTimer = new Timer(500,
kafkaSpoutConfig.getOffsetsCommitPeriodMs(), TimeUnit.MILLISECONDS);
}
refreshSubscriptionTimer = new Timer(500,
kafkaSpoutConfig.getPartitionRefreshPeriodMs(), TimeUnit.MILLISECONDS);
```
Here we are taking period as milliseconds consistently, and dropping
support nanoseconds on Timer means that up to 1 ms can be added to the period.
Unless we're expecting users to set these config values to small value like 1
or so, I think it doesn't matter. Indeed we're having 500 ms as default value,
which doesn't matter it will be 501 ms.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
