Use configured maximum memory to determine limits 01/37501/3
authorRobert Varga <rovarga@cisco.com>
Tue, 12 Apr 2016 14:51:59 +0000 (16:51 +0200)
committerTom Pantelis <tpanteli@brocade.com>
Mon, 6 Jun 2016 04:07:40 +0000 (04:07 +0000)
commit937708cd46aacd415b63d225782d804095721bc0
tree47fa5def089ac3b13cf3ccd48f7bf7fa4fb9366b
parent15d2db9a4b59b1e4c6a6d227d82d2595a061c6ba
Use configured maximum memory to determine limits

Use of Runtime.totalMemory() leads to different behavior as memory grows,
meaning we will perform different snapshots based on initial memory sizing
as well as the memory pressures from other parts of the system (which mean
the total memory will grow differently).

Use Runtime.maxMemory() instead, which will cause snapshotting to work
consistently with a fully-used system.

Change-Id: If6e4a135dc0b9a9d4795d1e5d75f7cbc60550c0d
Signed-off-by: Robert Varga <rovarga@cisco.com>
opendaylight/md-sal/sal-akka-raft/src/main/java/org/opendaylight/controller/cluster/raft/RaftActorContextImpl.java
opendaylight/md-sal/sal-distributed-datastore/src/main/yang/distributed-datastore-provider.yang