Bug 1288923 - [DOCS] [xPaaS] Document how to use the mesh configuration for A-MQ
[DOCS] [xPaaS] Document how to use the mesh configuration for A-MQ
Status: NEW
Product: Red Hat xPaaS
Classification: Red Hat
Component: Documentation (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: nshendye
Tomas Schlosser
Vikram Goyal
Depends On:
  Show dependency treegraph
Reported: 2015-12-06 21:35 EST by Vikram Goyal
Modified: 2016-07-29 00:10 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Vikram Goyal 2015-12-06 21:35:41 EST
In the A-MQ docs section about high availability and scalability [1], we need to document how to use the mesh configuration so that a network of brokers can be deployed.

Background thread on openshift-sme list: http://post-office.corp.redhat.com/archives/openshift-sme/2015-November/msg00880.html

GitHub Issue created: [2] (now closed).

The information to help with this (via email from Tomas Schlosser). Please also contact him at tschloss@redhat.com for any help with QE:

-- Start Forward --

Hello everyone,
yes, we have tested (and continue to do so) the mesh configuration with persistent setup. I can help Richard with debugging his environment, but I would need to get a bit more info.

I need:
- version of OpenShift
- version of templates
- version of docker image
- exact way of standing up A-MQ instance (from template - which? or through custom deploymentConfig - could I see it, please? or some other way?)

My initial guess is that you are missing mesh configuration options that are required:
- AMQ_MESH_DISCOVERY_TYPE (image jboss-amq-6/amq62-openshift only)
- AMQ_MESH_SERVICE_NAMESPACE (image jboss-amq-6/amq62-openshift only)

These environment variables are not in amq-persistent templates for a good reason. When you use persistent setup with A-MQ, you should not scale such pod, because it could share the persistent volume and cause issues when trying to get lock on shared kahadb store. Only way to create scaled persistent brokers is to create a few distinct brokers that all belong to the same service and use the deploymentConfig to set environment variables for clustering.

List of OpenShift resources:
service with selector cluster: my-cluster (e.g. amq-tcp pointing to port 61616)
persistentVolumeClaim named broker1-store
deploymentconfig with name broker1 using persistentVolumeClaim named broker1-store with label cluster: my-cluster
persistentVolumeClaim named broker2-store
deploymentconfig with name broker2 using persistentVolumeClaim named broker2-store with label cluster: my-cluster

Deployment configs would contain following environment variables:

This setup is hard to scale, but we don't support scaling down anyway (data will be lost) and scaling through usual OpenShift way is blocked by OpenShift's inability to share storage (or provide new persistentVolumeClaims for every replica).

-- End Forward --

[1] https://docs.openshift.com/enterprise/3.1/using_images/xpaas_images/a_mq.html#high-availability-and-scalability

[2] GH Issue: https://github.com/openshift/openshift-docs/issues/1272

Note You need to log in before you can comment on or make changes to this bug.