GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/413
NIFI-1745: Refactor how requests are replicated across cluster
This still has some work to be done, but I believe it's worth merging into
master now, only because we need to merge these changes with changes from a few
other branches, as we have some VERY large changesets going on.
NIFI-1745: Refactoring how HTTP Requests are replicated to nodes
Bug fixes and continuing to work on replication refactoring. Still need
to handle cluster locking and revisions
Begin work on RevisionManager
Resolved some issues that resulted from rebase
Fixed URIs to align with new URI's that will be used in 1.0.0
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-1745
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/413.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #413
----
commit 847b39f504226d7cc5cbb012214e3c964e8cbea8
Author: Mark Payne <[email protected]>
Date: 2016-03-24T15:49:08Z
NIFI-1678: Started refactoring heartbeating mechanism, using a new package:
org.apache.nifi.cluster.coordination
Added configuration options for ZooKeeper username & password for heartbeat
management. Also addressed issue where nodes that were previously disconnected
were asked to disconnect upon restart
Ensure that ACL is set properly when creating heartbeat node. Removed
unused ControllerStartupFailureMessage.java
Changed ZooKeeper ACL's so that container nodes that would not be sensitive
are wide open and removed the usage of username & password when communicating
with ZooKeeper. This was done specifically because username/password
combination is considered a 'testing' feature that should not be used in
production and is not supported by Apache Curator
Refactored CuratorHeartbeatMonitor into an abstract heartbeat monitor that
is responsible for processing heartbeats and CuratorHeartbeatMonitor that is
responsible for retrieving heartbeat information
Refactored so that heartbeats are sent to Cluster Coordinator directly
instead of to ZooKeeper. ZooKeeper is used to know which node is the cluster
coordinator but heartbeats to the Cluster Coordinator provide additional
information about the nodes.
commit 9f206bd1e9d6a90f26b914b20d2aad113a320aed
Author: Mark Payne <[email protected]>
Date: 2016-03-24T15:49:08Z
NIFI-1678: Started refactoring heartbeating mechanism, using a new package:
org.apache.nifi.cluster.coordination
commit 9a11af53297a46a38b9f1ee881d7e040d9f0f787
Author: Mark Payne <[email protected]>
Date: 2016-04-01T18:01:37Z
NIFI-1678: Added configuration options for ZooKeeper username & password
for heartbeat management. Also addressed issue where nodes that were previously
disconnected were asked to disconnect upon restart
commit 6d74740684c2b8e63d90de79411625fd177fcb40
Author: Mark Payne <[email protected]>
Date: 2016-04-06T17:56:55Z
NIFI-1678: Changed ZooKeeper ACL's so that container nodes that would not
be sensitive are wide open and removed the usage of username & password when
communicating with ZooKeeper. This was done specifically because
username/password combination is considered a 'testing' feature that should not
be used in production and is not supported by Apache Curator
commit fb5c00aea21062dc288587540c2d0509c3e17a61
Author: Mark Payne <[email protected]>
Date: 2016-04-08T12:17:11Z
NIFI-1727: Refactored logic for merging HTTP Requests that are federated
across cluster
commit e4cccbfce39ebd933be39898bf827a783c1c9273
Author: Mark Payne <[email protected]>
Date: 2016-04-12T13:43:13Z
NIFI-1745: Refactoring how HTTP Requests are replicated to nodes
Bug fixes and continuing to work on replication refactoring. Still need to
handle cluster locking and revisions
Begin work on RevisionManager
Resolved some issues that resulted from rebase
Fixed URIs to align with new URI's that will be used in 1.0.0
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
