Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This section first introduces the `Ensemble Manager` , then provides an ZooKeeper/Curator based example, and then concludes with The Fabric Ensemble ManagerBest Practices.

The Fabric Ensemble Manager

The Ensemble Manager dramatically minimises the Operational Complexities involved in creating, scaling, repairing and retiring ZooKeeper Ensembles.

Ensemble Views 

Ensembles currently hosted by a Service Fabric are listed under Entire's Ensembles view. 

...

ZooKeeper specific configuration for each Ensemble member may be seen by clicking on the Ensemble member's Server Id URI. 

Creating an Ensemble

To create a new Ensemble:

...

Note

In addition to name, the fibre list also displays each fibre's `Labels`. This information is useful when deciding the Ensemble's runtime topology: see The Fabric Ensemble ManagerBest Practices.

 

As shown, the `ZKExample` Ensemble is created with one member ( spark-infra-1.1).

...

Note

The Fabric Ensemble (e.g. myFabric) may be expanded or contract down to one member, but cannot be removed.

 

A ZK Curator based Example

This example demonstrates lock-coordination using the Curator locking example (see https://curator.apache.org/curator-examples/). In addition to the ZooKeeper clients demonstrating the use of the Curator library, the web system.part also demonstrates the use of Web Sockets and the new OSGi Alliances http whiteboard specification.

...

As shown each of the AppLayer fibres competes to acquire a lock from the ZKExample ensemble. The fibre that acquires the lock, decrements a shared counter and then releases the lock; then the process is then repeated.  All users of the application share a single countdown, and receive notifications of changes in state.

Ensemble Best Practices
Anchor
Ensemble Best Practices
Ensemble Best Practices

When creating ZooKeeper ensembles with Ensemble Manager, the usual best practices still apply:

...