It was a netvirt scale scenario. I had one openstack Control with 100 Computes, i.e., 100 OVSs. Had 1 private network and started creating VMs on each OVS. This causes a mesh of tunnels between all OVSs, which means I got to 10000 interfaces just for the tunnels, and a very big transport zone. I had a lot of flows too obviously.
-----Original Message----- From: Robert Varga [mailto:n...@hq.sk] Sent: Tuesday, January 10, 2017 10:21 PM To: Tom Pantelis <tompante...@gmail.com>; Sela, Guy <guy.s...@hpe.com> Cc: controller-dev@lists.opendaylight.org; odl netvirt dev <netvirt-...@lists.opendaylight.org> Subject: Re: [controller-dev] [mdsal-dev] Netvirt Scale tests: OutOfMemory from datastore On 01/10/2017 08:16 PM, Tom Pantelis wrote: > Since the length field of an array is an int, it's constrained to > Integer.MAX_VALUE (~2G). To handle snapshots larger than 2G we'll have > to chuck it into multiple byte[]. That could get funky on the reassembly side of things. If we go that route, we may as well switch to something more friendly, like java.nio.ByteBuffer(), too. Guy, just out of curiosity: how much duplication is in your data set? Regards, Robert _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
