You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a second configurable retry policy. The configuration now allows for a `human` and `robot` retry policy, intended for interactive use and scripts, respectively.
Copy file name to clipboardExpand all lines: doc/usage.rst
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,9 +52,14 @@ which are separated by newlines. The following keys are defined:
52
52
* if set to ``True``, when ``run_flow_on_task`` or similar methods are called a lookup is performed to see if there already exists such a run on the server. If so, download those results instead.
53
53
* if not given, will default to ``True``.
54
54
55
+
* retry_policy:
56
+
* Defines how to react when the server is unavailable or experiencing high load. It determines both how often to attempt to reconnect and how quickly to do so. Please don't use ``human`` in an automated script that you run more than one instance of, it might increase the time to complete your jobs and that of others.
57
+
* human (default): For people running openml in interactive fashion. Try only a few times, but in quick succession.
58
+
* robot: For people using openml in an automated fashion. Keep trying to reconnect for a longer time, quickly increasing the time between retries.
59
+
55
60
* connection_n_retries:
56
-
* number of connection retries.
57
-
* default: 2. Maximum number of retries: 20.
61
+
* number of connection retries
62
+
* default depends on retry_policy (5 for ``human``, 50 for ``robot``)
0 commit comments