You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current PulsarContainer's WaitStrategy includes waiting for the metrics endpoint to be available. The metrics endpoint is activated before the cluster and default tenants and namespaces are created. On slower systems (perhaps Apple M1 silicon running under Rosetta 2 for x86 arch), if your first step after the container is ready is to start interrogating the admin API, then certain calls may get unexpected responses.
I propose to instead check the admin clusters endpoint to ensure that the standalone cluster has actually been created.
The text was updated successfully, but these errors were encountered:
Module
Pulsar
Proposal
The current
PulsarContainer
'sWaitStrategy
includes waiting for the metrics endpoint to be available. The metrics endpoint is activated before the cluster and default tenants and namespaces are created. On slower systems (perhaps Apple M1 silicon running under Rosetta 2 for x86 arch), if your first step after the container is ready is to start interrogating the admin API, then certain calls may get unexpected responses.I propose to instead check the admin clusters endpoint to ensure that the
standalone
cluster has actually been created.The text was updated successfully, but these errors were encountered: