Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 79be540) | patch
Increase timeout on junits 71/77871/1
authorTschaen, Brendan <ctschaen@att.com>
Tue, 5 Feb 2019 13:40:03 +0000 (08:40 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 5 Feb 2019 13:47:07 +0000 (08:47 -0500)
commitc8b529749f19a1705a4fd0791eb83710c0b53e7d
tree7d4eadc2f19fe50f63504dde3acbe4f35e83f420tree | snapshot
parent79be54080739eb3ed05af26bb7b44efd2c252a47commit | diff
Increase timeout on junits

Issue-ID: MUSIC-309

Change-Id: Ic3d1095e4fa10da8ef06b62884db0c9e6ebb7612
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/test/java/org/onap/music/mdbc/mixins/MusicMixinTest.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.