Motivation

In #23683 and #23817, we handled the failure of ML PayloadProcessor.

But it maybe lead to message lost or out-of-order.

You can reproduce the issue via PublishWithMLPayloadProcessorTest:

1. Publish message-0 ~ message-9 to the topic and consume.
2. When enable message deduplication, we can consume the following messages:

Received message: message-0
Received message: message-1
Received message: message-2
Received message: message-4
Received message: message-5
Received message: message-6
Received message: message-7
Received message: message-8
Received message: message-9

The message-3 is lost
3. When disable message deduplication, we can consume the following messages:

Received message: message-0
Received message: message-1
Received message: message-2
Received message: message-4
Received message: message-5
Received message: message-6
Received message: message-7
Received message: message-8
Received message: message-9
Received message: message-0
Received message: message-1
Received message: message-2
Received message: message-3
Received message: message-4
Received message: message-5
Received message: message-6
Received message: message-7
Received message: message-8
Received message: message-9

** The message-3 is after message-4, message is out-of-order.

The key-point is we didn't fail all the incoming messages until Topic un-fenced.

Modifications

1. Fail all the incoming write request until topic un-fenced.
2. Add tests

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics
• Anything that affects deployment

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete