feat(sink): support sink rate limit for external sink

[hzxa21]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Closes #16253

Support SET SINK_RATE_LIMIT and ALTER SINK ... SET SINK_RATE_LIMIT for external sink. Sink into table is not supported.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

Support session config SET SINK_RATE_LIMIT to ... and ALTER SINK ... SET SINK_RATE_LIMIT to ... for external sink. Sink into table is not supported. See example in rate_limit.slt

[github-actions]

Hi, there.

📝 Telemetry Reminder:
If you're implementing this feature, please consider adding telemetry metrics to track its usage. This helps us understand how the feature is being used and improve it further.
You can find the function report_event of telemetry reporting in the following files. Feel free to ask questions if you need any guidance!

• src/frontend/src/telemetry.rs
• src/meta/src/telemetry.rs
• src/stream/src/telemetry.rs
• src/storage/compactor/src/telemetry.rs
  Or calling report_event_common (src/common/telemetry_event/src/lib.rs) as if finding it hard to implement.
  ✨ Thank you for your contribution to RisingWave! ✨

---

This is an automated comment created by the peaceiris/actions-label-commenter. Responding to the bot or mentioning it won't have any effect.

[tabVersion]

quick question: if the sink rate limit makes more data buffered in LogStore?

[hzxa21]

quick question: if the sink rate limit makes more data buffered in LogStore?

If sink decoupled is on, yes. If sink decoupled is off, it will cause backpressure.

[MrCroxx]

LGTM

[MrCroxx]

These logs are keep repeating. Let me try to fix.

2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed
2022-10-11T06:02:13.840593Z  WARN actor{otel.name="Actor 231" actor_id=231 prev_epoch=3160993419558912 curr_epoch=3160993541062656}:executor{otel.name="Sink E700000001"}: risingwave_connector::sink::log_store: rate limit control channel closed

[MrCroxx]

Should the log reader exit here? Seems there is no way to restore the rate limit control channel.

[MrCroxx]

Simulation recovery test passed with bail! here.

[MrCroxx]

Is it okay that I commit the fix directly in this PR?