Project

Profile

Help

Story #1915

closed

expose connect_timeout and read_timeout via configuration

Added by Anonymous over 6 years ago. Updated about 2 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Target Release - Nectar:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

My pulp installation was having issues completing synchronization of certain external repos due to timeouts. Following discussions on this thread[0], I found that I was able to resolve this timeout by increasing the values found in /usr/lib/python2.6/site-packages/nectar/config.py:22.

I'm hoping that these timeout values can be made available from a configuration file.

My patch diff (rpm python-nectar-1.5.1-1.el6.noarch):

22c22
<             connect_timeout=9.05, read_timeout=57, working_dir="/tmp"):
---
>             connect_timeout=6.05, read_timeout=27, working_dir="/tmp"):

[0] https://groups.google.com/forum/#!topic/foreman-users/J8xvzGHbz9w


Files

Actions #1

Updated by dkliban@redhat.com over 6 years ago

  • Tracker changed from Issue to Story
  • Groomed set to No
  • Sprint Candidate set to No
Actions #2

Updated by Anonymous about 6 years ago

related to #1758

Actions #3

Updated by bmbouter over 3 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #4

Updated by bmbouter over 3 years ago

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions #5

Updated by bmbouter over 3 years ago

  • Tags Pulp 2 added
Actions #8

Updated by Anonymous over 2 years ago

Nice information I have solved my problem [[Bollyquick]]

Also available in: Atom PDF