You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Erik Madrid <er...@civitaslearning.com> on 2017/05/09 04:57:02 UTC
configuration unit measurement inconsistencies
Hi!
I’ve noticied a few inconsistencies with respect to time measurement in configuration. Specifically:
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#cluster-common-properties
specifies
nifi.cluster.protocol.heartbeat.interval
The interval at which nodes should emit heartbeats to the Cluster Coordinator. The default value is 5 sec.
5 sec
whereas:
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#cluster-node-properties
specifies
nifi.cluster.node.connection.timeout
When connecting to another node in the cluster, specifies how long this node should wait before considering the connection a failure. The default value is 5 secs.
5 secs
Does plurality matter here? What should be considered valid - sec or secs?
Cheers!
Erik Madrid
erik.madrid@civitaslearning.com
Re: configuration unit measurement inconsistencies
Posted by Koji Kawamura <ij...@gmail.com>.
Hello Eric,
Plurality doesn't matter, "s", "sec", "secs", "second", "seconds" work the
same as implemented here:
https://github.com/apache/nifi/blob/master/nifi-commons/nifi-utils/src/main/java/org/apache/nifi/util/FormatUtils.java#L154
Thanks,
Koji
On Tue, May 9, 2017 at 1:57 PM, Erik Madrid <erik.madrid@civitaslearning.com
> wrote:
> Hi!
>
> I’ve noticied a few inconsistencies with respect to time measurement in
> configuration. Specifically:
>
> https://nifi.apache.org/docs/nifi-docs/html/administration-
> guide.html#cluster-common-properties
>
> specifies
>
> nifi.cluster.protocol.heartbeat.interval
> The interval at which nodes should emit heartbeats to the Cluster
> Coordinator. The default value is 5 sec.
> *5 sec*
>
> whereas:
>
> https://nifi.apache.org/docs/nifi-docs/html/administration-
> guide.html#cluster-node-properties
>
> specifies
> nifi.cluster.node.connection.timeout
> When connecting to another node in the cluster, specifies how long this
> node should wait before considering the connection a failure. The default
> value is *5 secs*.
> *5 secs*
>
>
> Does plurality matter here? What should be considered valid - sec or secs?
>
> Cheers!
> Erik Madrid
> erik.madrid@civitaslearning.com
>
>
>
>
Re: configuration unit measurement inconsistencies
Posted by Koji Kawamura <ij...@gmail.com>.
Hello Eric,
Plurality doesn't matter, "s", "sec", "secs", "second", "seconds" work the
same as implemented here:
https://github.com/apache/nifi/blob/master/nifi-commons/nifi-utils/src/main/java/org/apache/nifi/util/FormatUtils.java#L154
Thanks,
Koji
On Tue, May 9, 2017 at 1:57 PM, Erik Madrid <erik.madrid@civitaslearning.com
> wrote:
> Hi!
>
> I’ve noticied a few inconsistencies with respect to time measurement in
> configuration. Specifically:
>
> https://nifi.apache.org/docs/nifi-docs/html/administration-
> guide.html#cluster-common-properties
>
> specifies
>
> nifi.cluster.protocol.heartbeat.interval
> The interval at which nodes should emit heartbeats to the Cluster
> Coordinator. The default value is 5 sec.
> *5 sec*
>
> whereas:
>
> https://nifi.apache.org/docs/nifi-docs/html/administration-
> guide.html#cluster-node-properties
>
> specifies
> nifi.cluster.node.connection.timeout
> When connecting to another node in the cluster, specifies how long this
> node should wait before considering the connection a failure. The default
> value is *5 secs*.
> *5 secs*
>
>
> Does plurality matter here? What should be considered valid - sec or secs?
>
> Cheers!
> Erik Madrid
> erik.madrid@civitaslearning.com
>
>
>
>