[SERVER-54463] Override CatalogClient's default timeout Created: 11/Feb/21 Updated: 02/Jun/21 Resolved: 02/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding EMEA 2021-05-31, Sharding EMEA 2021-06-14 |
| Participants: |
| Description |
|
By default, the catalog client is executing operations with a 30 seconds timeout taken from Shard::kDefaultConfigCommandTimeout. Since we don't want DDL operations to block half-way, that timeout must be increased (no time limit at all?). |
| Comments |
| Comment by Pierlauro Sciarelli [ 02/Jun/21 ] |
|
Closing because the timeout is now handled in the new DDL coordinator ( |
| Comment by Tommaso Tocci [ 18/Feb/21 ] |
|
WFBF day goal: decide how to fix. |