Change Details

The sopel timeout is currently 120s. This is probably too low and causing a hightened rate of false timeout detections and inceased risk of crash during a network wobble. I plan to raise the timeout value on both tools in a rolling fashion over the next few weeks to avoid impact. | Instance | Date | New Value | Test | 22 Apr | 210 | Prod | 27 Apr | 210 | Test | 28 Apr | 240 | Prod | 29 Apr | 240 | Test | 30 Apr | 270 | Prod | 1 May | 270 | Test | 4 May | 300 | Prod | 5 May | 300

The sopel timeout is currently 120s. This is probably too low and causing a hightened rate of false timeout detections and inceased risk of crash during a network wobble. I plan to raise the timeout value on both tools in a rolling fashion over the next few weeks to avoid impact. | Instance | Date | New Value | Test | 22 Apr | 210 | Prod | 29 Apr | 210 | Test | 30 Apr | 240 | Prod | 1 May | 240 | Test | 4 May | 270 | Prod | 5 May | 270 | Test | 6 May | 300 | Prod | 7 May | 300

The sopel timeout is currently 120s. This is probably too low and causing a hightened rate of false timeout detections and inceased risk of crash during a network wobble. I plan to raise the timeout value on both tools in a rolling fashion over the next few weeks to avoid impact. | Instance | Date | New Value | Test | 22 Apr | 210 | Prod | 279 Apr | 210 | Test | 2830 Apr | 240 | Prod | 29 Apr1 May | 240 | Test | 30 Apr4 May | 270 | Prod | 15 May | 270 | Test | 46 May | 300 | Prod | 57 May | 300