search

risingwavelabs / risingwave

Best-in-class stream processing, analytics, and management. Perform continuous analytics, or build event-driven applications, real-time ETL pipelines, and feature stores in minutes. Unified streaming and batch. PostgreSQL compatible.
https://www.risingwave.com/slack
Apache License 2.0
6.76k stars 557 forks source link

Discussion: make `timeout` configurations easier to track #6226

Open lmatz opened 1 year ago

lmatz commented 1 year ago

There are many timeout variables in the codebase, if the network communication timeout, it may produce a failure, trigger retry or recover, etc.

As we now want to introduce chaos engineering to test RisingWave, we want to make sure the network delay or the time of network partition introduced by Chaos is long enough to cover these cases.

So intend to make tracking these timeout variables easier:

  1. make hardcoded values into a named const variable and give them the same prefix or suffix to their variable name. or
  2. make them configurable in the developer subsection of src/config/risingwave.toml.
github-actions[bot] commented 1 year ago

This issue has been open for 60 days with no activity. Could you please update the status? Feel free to continue discussion or close as not planned.