Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: afb06f6) | patch
Split partition using MRU 09/91109/5
authorTschaen, Brendan <ctschaen@att.com>
Tue, 9 Jul 2019 19:02:22 +0000 (15:02 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 25 Jul 2019 17:45:46 +0000 (13:45 -0400)
commit32dbfd3759fc2aa20e8f03637b8fcc281c3730e2
treeb55da82bce91ea05df0e7a5e3aefaa0591fc5feetree | snapshot
parentafb06f611545e83494622f6a16f6966b93c0e418commit | diff
Split partition using MRU

Most recently used approach to splitting a partition.
Split happens when committing, we see what we've used
from existing partition and splits accordingly. This
feature is configurable via the mdbc.properties file.

Issue-ID: MUSIC-404
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
Change-Id: Ie33f4d1ae0e6253678062558015c2a10c4fae614
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcConnection.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcServer.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicInterface.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicMixin.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MySQLMixin.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ownership/OwnershipAndCheckpoint.java diff | blob | history
mdbc-server/src/main/resources/mdbc.properties diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/MdbcTestUtils.java diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/mixins/MySQLMixinTest.java diff | blob | history
The most crucial recipe is a multi-site database cache (mdbc) that enable ONAP components that maintain state in a SQL database to avail the benefits of MUSIC without compromising their need to use transactional SQL DBs. These ONAP components can rely on existing db clustering techniques like MariaDB for transactionality and complex querying within a site. mdbc will intercept each of these read/write calls to the db cluster and mirror this state to other geo-distributed sites through MUSIC either synchronously or asynchronously (configurable at a table-level). For example, components like the ONAP Service Orchestrator that use MariaDB to maintain state can directly use this recipe with no change to their SQL code.