[ovs-discuss] conf.db large than 400M, is that a problem?

[Huanglili (lee)]

En, found ovsdb_file_commit() function is ovsdb/file.c:

    /* If it has been at least COMPACT_MIN_MSEC ms since the last time we
     * compacted (or at least COMPACT_RETRY_MSEC ms since the last time we
     * tried), and if there are at least 100 transactions in the database, and
     * if the database is at least 10 MB, then compact the database. */

Thanks a lot.

-----邮件原件-----
发件人: Ben Pfaff [mailto:blp at ovn.org] 
发送时间: 2017年3月8日 12:42
收件人: Huanglili (lee)
抄送: ovs-discuss at openvswitch.org; gaoxiaoqiu; caihe
主题: Re: [ovs-discuss] conf.db large than 400M, is that a problem?

On Wed, Mar 08, 2017 at 01:33:48AM +0000, Huanglili (lee) wrote:
> When I do some tests, I found a strange thing that /etc/openvswitch/conf.db could be 432M.
> What I did is:
> while(1);do
> create a ovs bridge
> create a internal port
> delete bridge
> service openvswitch restart
> done
> 
> But when I do
> while(1);do
> create a ovs bridge
> create a internal port
> delete bridge
> #service openvswitch restart
> done
> conf.db will increase to 50M mostly and then be reduced to 400K automatically.
> 
> what's the difference?

When ovsdb-server runs, it will periodically compact the database if it grows large.  But it has to run a while before it does that.  If you constantly restart it, it won't get around to it.