I've encountered a minor issue during the graceful shutdown of an application that uses the Topic API.
My application is blocked, waiting for a message on reader.ReadMessage(ctx). When the application begins its shutdown sequence, the context (ctx) is canceled. As a result, I get a WARN log entry:
topic read messages failed
This doesn't seem like the correct behavior. Context cancellation is a standard and expected part of a graceful shutdown procedure. Therefore, the driver shouldn't log this event as a warning, as it's not an unexpected failure but a deliberate, controlled termination.
The same behavior is observed with the following messages:
table session delete failed
topic reader data response received and process failed
I've encountered a minor issue during the graceful shutdown of an application that uses the Topic API.
My application is blocked, waiting for a message on reader.ReadMessage(ctx). When the application begins its shutdown sequence, the context (ctx) is canceled. As a result, I get a WARN log entry:
topic read messages failedThis doesn't seem like the correct behavior. Context cancellation is a standard and expected part of a graceful shutdown procedure. Therefore, the driver shouldn't log this event as a warning, as it's not an unexpected failure but a deliberate, controlled termination.
The same behavior is observed with the following messages:
table session delete failedtopic reader data response received and process failed