Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 6f363a8) | patch
Warm up ranges across sites 24/82824/2
authorTschaen, Brendan <ctschaen@att.com>
Wed, 20 Mar 2019 16:12:06 +0000 (12:12 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Wed, 20 Mar 2019 20:26:05 +0000 (16:26 -0400)
commita290a037ea6da2dc062945f77240a10564f6541f
tree506e46c1fbdb73d62ec145998690c17869c7b366tree | snapshot
parent6f363a89863a91ac104e5c77f0096636a8db5343commit | diff
Warm up ranges across sites

Add configuration to select which ranges we warm up. Default (null) is all ranges

Change-Id: I0f241563959cc9fb673ab6d8a87c45e8399086c2
Issue-ID: MUSIC-287
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/pom.xml diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/Configuration.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/StateManager.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/examples/MdbcTestClient.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/DBInterface.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/java/org/onap/music/mdbc/tables/MusicTxDigest.java diff | blob | history
mdbc-server/src/main/resources/music.properties diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/StateManagerTest.java [new file with mode: 0644] blob
mdbc-server/src/test/resources/mockito-extensions/org.mockito.plugins.MockMaker [new file with mode: 0644] blob
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.