On Tue, Mar 12, 2024 at 8:42 PM Timothy Bish wrote:
> On 3/12/24 16:25, Ciaran wrote:
> > On Tue, Mar 12, 2024 at 7:13 PM Timothy Bish
> wrote:
> >
> >> On 3/12/24 04:08, Ciaran wrote:
> >>> On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish
> >> wrote:
> The client re-connection logic treats a
On 3/12/24 16:25, Ciaran wrote:
On Tue, Mar 12, 2024 at 7:13 PM Timothy Bish wrote:
On 3/12/24 04:08, Ciaran wrote:
On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish
wrote:
The client re-connection logic treats a SASL authentication error as a
terminal state and will not continue reconnect
On Tue, Mar 12, 2024 at 7:13 PM Timothy Bish wrote:
> On 3/12/24 04:08, Ciaran wrote:
> > On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish
> wrote:
> >
> >>
> >> The client re-connection logic treats a SASL authentication error as a
> >> terminal state and will not continue reconnect attempts if it
On 3/12/24 04:08, Ciaran wrote:
On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish wrote:
The client re-connection logic treats a SASL authentication error as a
terminal state and will not continue reconnect attempts if it receives a
SASL outcome that indicates anything other than a temporary
On Mon, Mar 11, 2024 at 9:33 PM Timothy Bish wrote:
>
>
> The client re-connection logic treats a SASL authentication error as a
> terminal state and will not continue reconnect attempts if it receives a
> SASL outcome that indicates anything other than a temporary failure
> state so it should
