Clustering Kylo

Kylo Clustering is now available starting with version v0.8.1.

Kylo uses jgroups,, for cluster configuration. This is chosen because Kylo’s metadata engine, Modeshape ( uses jgroups internally for its cluster management.

Two jgroups configuration files are needed to be setup (One for ModeShape and one for Kylo)

ModeShape Configuration

  1. Update the metadata-repository.json file and add the “clustering” section

     "clustering": {

    Make sure the name of the jgroups-config.xml file is in the /kylo-services/conf folder. Refer sample files for setting up a jgroups configuration at /opt/kylo/setup/config/kylo-cluster. Note if working in Amazon you need to refer to the “s3” jgroups configuration as it needs to use an S3Ping to have the nodes communicate with each other.

Kylo Configuration

We also have another jgroups configuration setup for Kylo nodes. We cannot use the ModeShape cluster configuration since that is internal to ModeShape.

1. Create a similar jgroup-config.xml file and add it to the /kylo-services/conf file. Refer sample files for setting up a jgroups configuration at /opt/kylo/setup/config/kylo-cluster. Ensure the ports are different between this xml file and the ModeShape xml file

  1. Add a property to the kylo-services/conf/ to reference this file
  1. Startup Kylo

When starting up you should see 2 cluster configurations in the logs. One for the modeshape cluster and one for the kylo cluster

GMS: address=Kylo - MUSSR186054-918-31345, cluster=kylo-modeshape-cluster, physical address=
GMS: address=Kylo - MUSSR186054-918-31345, cluster=internal-kylo-cluster, physical address=
2017-05-04 06:17:06 INFO  pool-5-thread-1:JGroupsClusterService:120 - Cluster membership changed: There are now 1 members in the cluster. [Kylo - MUSSR186054-918-31345]
2017-05-04 06:17:06 INFO  pool-5-thread-1:JGroupsClusterService:155 - *** Channel connected Kylo - MUSSR186054-918-31345,[Kylo - MUSSR186054-918-31345]
2017-05-04 06:17:06 INFO  pool-5-thread-1:NifiFlowCacheClusterManager:205 - on connected 1 members exist.  [Kylo - MUSSR186054-918-31345]

Quartz Scheduler Configuration

When running in clustered mode you need to configure the Quartz SLA scheduler to be backed by the database and run it in clustered mode. Do the following:

  1. Download and extract the Quartz distribution to a machine. You just need this to get the database scripts.
  2. Run the Quartz database scripts for your database found in the docs/dbTables
  3. Create a file and put it in the /opt/kylo/kylo-services/conf folder. Refer to a sample file /opt/kylo/setup/kylo-cluster/
    1. Do not specify datasource connection information in this file. The system will use the default spring.datasource property information found in the for the database connection

Service Monitoring

You can monitor the health of the kylo cluster by adding the kylo-service-monitor-kylo-cluster.jar to the /opt/kylo/kylo-services/plugins folder.

  1. Copy the file in the /opt/kylo/setup/plugins/kylo-service-monitor-kylo-cluster-VERSION.jar to the /opt/kylo/kylo-services/plugins` folder
  2. Add a new property to the to indicate the expected number of nodes you are running in your cluster. Below is an example expecting 2 nodes in the cluster
  1. Now a new Kylo Cluster service will appear in the Kylo dashboard and show you cluster health status




  • If you are having issues identifying if the clustering is working you can modify the and have it show cluster events. This is especially useful for modeshape. Note: by doing this logs will be very verbose, so its recommended this is only done for initial setup/debugging
  • If you get a Network is unreachable error, below, you may need to do the following:

    • Network unreachable error

      SEVERE: JGRP000200: failed sending discovery request Network is unreachable
          at Method)
          at org.jgroups.protocols.MPING.sendMcastDiscoveryRequest(
          at org.jgroups.protocols.PING.sendDiscoveryRequest(
          at org.jgroups.protocols.PING.findMembers(
          at org.jgroups.protocols.Discovery.findMembers(
    • Modify the /opt/kylo/kylo-services/bin/

    • Add

      java $KYLO_SERVICES_OPTS -cp /opt/kylo/kylo-services/conf ....
  • Multicast

    • Enabling multicast is done via the <MPING .. /> xml node in the jgroups-configuration xml file. Multicast may not work in your environment. If you have issues you can remove the <MPING ../> node and ensure your host names are configured propertly in the <TCPPING ../> node. Refer to the jgroups documentation around MPING for more information:
  • Running the Multicast test program

    1. Stop kylo-services on both nodes

    2. On 1 node run the code below to act as a receiver. Replace the bind_addr and port arguments with your specific values

      java  -cp  /opt/kylo/kylo-services/conf:/opt/kylo/kylo-services/lib/*:/opt/kylo/kylo-services/plugin/* org.jgroups.tests.McastReceiverTest -bind_addr -port 7900
    3. On another node run the code below to act as a sender. Replace the bind_addr and port arguments to match the values above

      java -cp  /opt/kylo/kylo-services/conf:/opt/kylo/kylo-services/lib/*:/opt/kylo/kylo-services/plugin/* org.jgroups.tests.McastSenderTest -bind_addr -port 7900

    As a Sender you will get a prompt. Type in some string and then verify its received on the other node.


    org.jgroups.tests.McastSenderTest -bind_addr -port 7900
    Socket #1=, ttl=32, bind interface=/
    > this is a test message


    this is a test message [sender=]