Hello,
I believe this commit introduced a regression, not directly in OVN itself but in
the OVN ML2 driver in OpenStack. Since OpenStack is a reference CMS for OVN, I
believe it could be essential to mention this regression here. At least
OpenStack releases from Ussuri to Yoga are affected.
Hi Numan,
according to our experience, in such case the connection can never be fully
established, and northd ends up being in an endless loop with 100% CPU
utilization.
Numan Siddique schrieb am Sa., 18. Sept. 2021, 00:05:
> On Fri, Sep 17, 2021 at 5:02 PM Renat Nurgaliyev
>
currently
there is no way to control it before the database connection is made, and
if it cannot be made, it is too late to try to control it.
Thanks,
Renat.
Han Zhou schrieb am Fr., 17. Sept. 2021, 23:55:
>
>
> On Fri, Sep 17, 2021 at 1:48 PM Renat Nurgaliyev
> wrote:
>
Hello Han,
when I wrote this patch we had an issue with a very big SB database, around
1,5 gigabytes. There were no controllers or northds running, so the
database server was without any load at all. Although OVSDB was idling,
even a single northd process could not fully connect to the database
Setting probe interval before calling Reconnect.enable() ensures
that initial OVSDB connection will not use the default probe interval
of 5000 ms, as it may cause connection problems to large databases.
Signed-off-by: Renat Nurgaliyev
---
python/ovs/jsonrpc.py | 9 +
1 file changed, 5
On Tue, Dec 01, 2020 at 11:41:29AM +0100, Dumitru Ceara wrote:
> On 12/1/20 10:41 AM, Renat Nurgaliyev wrote:
> > On Mon, Nov 30, 2020 at 12:28:56PM -0800, Han Zhou wrote:
> >> On Mon, Nov 30, 2020 at 12:13 PM Renat Nurgaliyev
> >> wrote:
> >>>
> &
On Mon, Nov 30, 2020 at 12:28:56PM -0800, Han Zhou wrote:
> On Mon, Nov 30, 2020 at 12:13 PM Renat Nurgaliyev
> wrote:
> >
> > On 30.11.20 07:07, Numan Siddique wrote:
> > > On Mon, Nov 30, 2020 at 7:37 AM Han Zhou wrote:
> > >> On Sat, Nov 28, 2020 at
20 at 4:11 PM Daniel Alvarez Sanchez
wrote:
On Wed, Nov 25, 2020 at 7:59 PM Dumitru Ceara
wrote:
On 11/25/20 7:06 PM, Numan Siddique wrote:
On Wed, Nov 25, 2020 at 10:24 PM Renat Nurgaliyev
wrote:
On 25.11.20 16:14, Dumitru Ceara wrote:
On 11/25/20 3:30 PM, Renat Nurgaliyev wrote:
He
On 25.11.20 16:14, Dumitru Ceara wrote:
On 11/25/20 3:30 PM, Renat Nurgaliyev wrote:
Hello folks,
Hi Renat,
we run a lab where we try to evaluate scalability potential of OVN with
OpenStack as CMS.
Current lab setup is following:
500 networks
500 routers
1500 VM ports (3 per network
Hello folks,
we run a lab where we try to evaluate scalability potential of OVN with
OpenStack as CMS.
Current lab setup is following:
500 networks
500 routers
1500 VM ports (3 per network/router)
1500 Floating IPs (one per VM port)
There is an external network, which is bridged to
-server will refuse to work
with the database file. This is especially critical for OVN southbound
database, since it tends to grow rapidly.
Signed-off-by: Renat Nurgaliyev
---
v2:
replace size_t with uint32_t where necessary instead of explicit cast
---
lib/sha1.c | 4 ++--
lib/sha1.h | 4
On 13.11.20 15:03, Ilya Maximets wrote:
On 11/12/20 4:51 PM, Renat Nurgaliyev wrote:
Missing cast to 32 bits in overflow check makes this conditional never
be true. Because of this, computation of SHA-1 checksum will be wrong
for any data that is bigger than 512 megabytes, which in bits
, with
transactions bigger than 512 megabytes, is considered corrupt and
ovsdb-server will refuse to work with the database.
Signed-off-by: Renat Nurgaliyev
---
lib/sha1.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/sha1.c b/lib/sha1.c
index 4f48ef210..4889c976b 100644
DEFAULT_PROBE_INTERVAL_MSEC is applied correctly.
Signed-off-by: Renat Nurgaliyev
---
v2:
- Resubmitting patch because git am failed last time
v3:
- Resubmitting patch because mail client broke formatting
v4:
- Resubmitting patch because mail client broke formatting once again.
I switched to mutt and it won't
DEFAULT_PROBE_INTERVAL_MSEC is applied correctly.
Signed-off-by: Renat Nurgaliyev
---
v2:
- Resubmitting patch because git am failed last time
v3:
- Resubmitting patch because mail client broke formatting
v4:
- Resubmitting patch because mail client broke formatting once again.
I switched to mutt and it won't
DEFAULT_PROBE_INTERVAL_MSEC is applied correctly.
Signed-off-by: Renat Nurgaliyev
---
v2:
- Resubmitting patch because git am failed last time
v3:
- Resubmitting patch because mail client broke formatting
---
northd/ovn-northd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/northd/ovn
DEFAULT_PROBE_INTERVAL_MSEC is applied correctly.
Signed-off-by: Renat Nurgaliyev
---
v2:
- Resubmitting patch because git am failed last time
---
northd/ovn-northd.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/northd/ovn-northd.c b/northd/ovn-northd.c
index 684c2bd47..073c6a0f3 100644
From: Renat Nurgaliyev
Before the value configured in northd_probe_interval can be actually
applied, connection to both northbound and southbound databases must be
established. In big scale environments, the southbound database can be so
big that northd cannot establish connection in 5 seconds
18 matches
Mail list logo
