On 4/10/24 17:48, Chris Riches wrote:
> If the database is particularly large (multi-GB), ovsdb-server can take
Hi, Chris. May I ask how did you end up with multi-GB database?
I would understand if it was an OVN Southbound DB, for example,
but why the local database that only stores ports/bridges and
some other not that large things ends up with so much data?
Sounds a little strange.
Best regards, Ilya Maximets.
> several minutes to come up. This tends to fall afoul of the default
> systemd start timeout, which is typically 90s, putting the service into
> an infinite restart loop.
>
> To avoid this, set the timeout to a more generous 5 minutes.
>
> This change brings ovsdb-server's timeout in line with ovs-vswitchd,
> which got the same treatment in commit c1c69e8a45 ("rhel/systemd: Set
> ovs-vswitchd timeout to 5 minutes").
>
> Signed-off-by: Chris Riches <chris.ric...@nutanix.com>
> ---
> rhel/usr_lib_systemd_system_ovsdb-server.service | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/rhel/usr_lib_systemd_system_ovsdb-server.service
> b/rhel/usr_lib_systemd_system_ovsdb-server.service
> index 49dc06e38..558632320 100644
> --- a/rhel/usr_lib_systemd_system_ovsdb-server.service
> +++ b/rhel/usr_lib_systemd_system_ovsdb-server.service
> @@ -29,3 +29,4 @@ ExecStop=/usr/share/openvswitch/scripts/ovs-ctl
> --no-ovs-vswitchd stop
> ExecReload=/usr/share/openvswitch/scripts/ovs-ctl --no-ovs-vswitchd \
> ${OVS_USER_OPT} \
> --no-monitor restart $OPTIONS
> +TimeoutSec=300
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
