This is an automated email from the ASF dual-hosted git repository. rombert pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/sling-org-apache-sling-discovery-api.git
commit c6ce72cedd331faabe85240016a073f8024971b6 Author: Stefan Egli <stefane...@apache.org> AuthorDate: Mon Apr 27 13:12:03 2015 +0000 SLING-4668 : following clarifying note added to getId: 'Addition in 1.0.4: this id must consist only of alphanumeric characters plus dash '-' and underscore '_'. git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1676252 13f79535-47bb-0310-9956-ffa450edef68 --- .../org/apache/sling/discovery/ClusterView.java | 63 +++++++++++----------- 1 file changed, 33 insertions(+), 30 deletions(-) diff --git a/src/main/java/org/apache/sling/discovery/ClusterView.java b/src/main/java/org/apache/sling/discovery/ClusterView.java index f50612b..3914fcf 100644 --- a/src/main/java/org/apache/sling/discovery/ClusterView.java +++ b/src/main/java/org/apache/sling/discovery/ClusterView.java @@ -31,27 +31,30 @@ import aQute.bnd.annotation.ProviderType; @ProviderType public interface ClusterView { - /** - * Returns a stable id of the cluster represented by this - * cluster view. - * <p> - * Similar to the SlingID, this id is persisted and thus - * remains stable accross instance/cluster restarts. - * <p> - * When an instance joins a cluster, it will inherit - * the id from the joined cluster (thus incurs a cluster id - * change). - * <p> - * Note: When instances part from a cluster (eg due to a network - * partitioning) the cluster id is retained. This results in - * potentially multiple clusters with the same id. This - * fact could be used to detect such partitioning/split brain - * situations. It also implies though that the cluster id - * is not guaranteed to be unique in a topology! - * @return an id of this cluster view - * @see <a href="http://issues.apache.org/jira/browse/SLING-3164">SLING-3164</a> - * @since exists since 1.0.0 - stable since 1.0.2 - */ + /** + * Returns a stable id of the cluster represented by this + * cluster view. + * <p> + * Similar to the SlingID, this id is persisted and thus + * remains stable accross instance/cluster restarts. + * <p> + * When an instance joins a cluster, it will inherit + * the id from the joined cluster (thus incurs a cluster id + * change). + * <p> + * Note: When instances part from a cluster (eg due to a network + * partitioning) the cluster id is retained. This results in + * potentially multiple clusters with the same id. This + * fact could be used to detect such partitioning/split brain + * situations. It also implies though that the cluster id + * is not guaranteed to be unique in a topology! + * <p> + * Addition in 1.0.4: this id must consist only of alphanumeric + * characters plus dash '-' and underscore '_'. + * @return an id of this cluster view + * @see <a href="http://issues.apache.org/jira/browse/SLING-3164">SLING-3164</a> + * @since exists since 1.0.0 - stable since 1.0.2 - alphanumeric + '_' and'-' since 1.0.4 + */ String getId(); /** @@ -64,14 +67,14 @@ public interface ClusterView { */ List<InstanceDescription> getInstances(); - /** - * Provides the InstanceDescription belonging to the leader instance. - * <p> - * Every ClusterView is guaranteed to have one and only one leader. - * <p> - * The leader is stable: once a leader is elected it stays leader - * unless it leaves the cluster (due to shutdown/crash/network problems) - * @return the InstanceDescription belonging to the leader instance - */ + /** + * Provides the InstanceDescription belonging to the leader instance. + * <p> + * Every ClusterView is guaranteed to have one and only one leader. + * <p> + * The leader is stable: once a leader is elected it stays leader + * unless it leaves the cluster (due to shutdown/crash/network problems) + * @return the InstanceDescription belonging to the leader instance + */ InstanceDescription getLeader(); } -- To stop receiving notification emails like this one, please contact "commits@sling.apache.org" <commits@sling.apache.org>.