KAFKA-7177: Update 2.0 documentation to reflect changed quota behaviors by KIP-219

[jonlee2]

Updated the 2.0 document for changed quota behaviors.

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[jonlee2]

@lindong28 Can you review? Thanks.

[lindong28]

We probably should change or remove the sentence that says This approach keeps the quota violation transparent to clients (outside of client-side metrics). This also keeps them from having to implement any special backoff and retry behavior which can get tricky. In fact, bad client behavior (retry without backoff) can exacerbate the very problem quotas are trying to solve.

[jonlee2]

Remove those sentences. @lindong28 Can you take a look again? Thanks.

[lindong28]

@jonlee2 LGTM in terms of its content. I think client layer should probably just be client.

@ijuma You have much better english writing than me. Since this touches the design doc that user reads, would you have time to take a look?

[ijuma]

Thanks for the PR. I think it would be useful to explain the reasoning of the approach a little. For example, this still handles badly behaved clients by relying on socket buffer back pressure.

[jonlee2]

Updated the text as suggested. @lindong28 @ijuma Can you take another look? Thanks.

[lindong28]

Thanks for update. LGTM. @ijuma may have better ideas of writing.

[asfgit]

FAILURE
9189 tests run, 5 skipped, 1 failed.
--none--

[lindong28]

I just merged it to trunk so that we can use the design doc for 2.0 release. We can have minor followup patch to improve the doc if needed.

[ijuma]

Seems fine to me, thanks.