GitHub user visortelle edited a comment on the discussion: What is the intended
result of creating a cluster via PUT /admin/v2/clusters/{cluster-name}?
@dameiss-tibco hi 👋
You'll need to use these cluster names in further operations. For example, the
"create tenant" operation requires at least one allowed cluster. The "create
namespace" operation also requires clusters when you have at least two clusters
in your Pulsar instance.
> with completely bogus values for brokerServiceUrl and serviceUrl, and the
> cluster is created. But it is obviously not useable since the URLs are invalid
<img width="1438" alt="Screenshot 2024-04-26 at 8 36 57 PM"
src="https://github.com/apache/pulsar/assets/9302460/662547af-26c7-4061-98dc-0ed85e096da6";>
>From the screenshot above you can see that there is some URL validation. At
>the same time, you're right that the cluster you register may be unavailable
>at the moment of its registration in another cluster.
In practice, it doesn't introduce any problems. It seems a completely valid
behavior to me for a distributed system that should continue to work where some
component unexpectedly become unavailable, e.g. one of the clusters is down.
Example unrelated to Pulsar. Imagine two services A and B where each should
know about another to work properly. If you make the availability check on
service start, you're in trouble. If on starting service A you'd check that
service B is available, and service B would check that service A is available,
they both wouldn't be able to start due to a cyclic dependency.
You can consider the cluster registration a similar case to the example above,
but the configuration is dynamic.
GitHub link:
https://github.com/apache/pulsar/discussions/22602#discussioncomment-9239830
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
