-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PAYARA-618 Enable the DAS to discover Payara Micro instances #1152
PAYARA-618 Enable the DAS to discover Payara Micro instances #1152
Conversation
…viate race condition
Might be worth refactoring the package and module names, as it's no longer just for Payara Micro. |
Jenkins test please |
1 similar comment
Jenkins test please |
All tests have passed |
This PR also changes the behaviour of the A new profile is also introduced to split out the MicroProfile build from that of Micro: |
Jenkins test please |
All tests have passed |
Allows the DAS to view information about the Payara Server and Payara Micro instances in the Hazelcast cluster.
Introduces a new Asadmin command,
list-hazelcast-cluster-members
, that lists information about the instances in the domain's Hazelcast cluster:Usage:
list-hazelcast-cluster-members [--type=type]
The
--type
option accepts a String of micro or server, and filters the result to only list information about Payara Micro or Payara Server instances respectively.This PR also modifies the Hazelcast -> Cluster Members page under Domain (formally could be found under server) in the Admin Console to display the new information.
Also moves configuration of Hazelcast for the DAS from server into Domain, as we're looking to move to a model with a single Hazelcast domain-wide cluster utilising deployment groups over having a separate hazelcast configuration for each instance.