|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1939 | minor | always | 08-13-07 16:19 | 09-06-07 10:43 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.23 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.3 | ||
|
|
|||||
| Summary: | 0001939: load balancer timeouts | ||||
| Description: |
(rep by Bradley Van Cleave) We made these changes on the Load Balancer, but we are still seeing the Broken Pipe Exception in the logs. <!-- Did not change value --> <client-read-timeout>120s</client-read-timeout> <!-- Added value --> <client-live-time>135s</client-live-time> <!-- Added read-timeout --> <srun server-id="..." host="..." port="6880" read-timeout="180s"/> <srun server-id="..." host="..." port="6880" read-timeout="180s"/> I didn't change the value for the client-read-timeout. Should this value be the same as the client-live-time? I didn't see any large GCs. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| There are no notes attached to this issue. |