nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From markap14 <...@git.apache.org>
Subject [GitHub] nifi pull request #491: NIFI-1960: Update admin guide regarding documentatio...
Date Fri, 03 Jun 2016 18:46:08 GMT
Github user markap14 commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/491#discussion_r65757147
  
    --- Diff: nifi-docs/src/main/asciidoc/administration-guide.adoc ---
    @@ -1351,66 +1389,81 @@ in the file specified in `nifi.login.identity.provider.configuration.file`.
Sett
     |nifi.security.ocsp.responder.certificate|This is the location of the OCSP responder
certificate if one is being used. It is blank by default.
     |====
     
    -*Cluster Common Properties* +
    +==== Cluster Common Properties
     
    -When setting up a NiFi cluster, these properties should be configured the same way on
both the cluster manager and the nodes.
    +When setting up a NiFi cluster, these properties should be configured the same way on
all nodes.
     
     |====
     |*Property*|*Description*
    -|nifi.cluster.protocol.heartbeat.interval|The interval at which nodes should emit heartbeats
to the cluster manager. The default value is 5 sec.
    +|nifi.cluster.protocol.heartbeat.interval|The interval at which nodes should emit heartbeats
to the Cluster Coordinator. The default value is 5 sec.
     |nifi.cluster.protocol.is.secure|This indicates whether cluster communications are secure.
The default value is _false_.
    -|nifi.cluster.protocol.socket.timeout|The amount of time to wait for a cluster protocol
socket to be established before trying again. The default value is 30 sec.
    -|nifi.cluster.protocol.connection.handshake.timeout|The amount of time to wait for a
node to connect to the cluster. The default value is 45 sec.
    +|nifi.cluster.node.event.history.size|When the state of a node in the cluster is changed,
an event is generated
    --- End diff --
    
    Yes - I updated this in the new commit.


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message