Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: dcdded9) | patch
Add retry to Music get calls 82/90482/2
authorArthur Martella <arthur.martella.1@att.com>
Tue, 25 Jun 2019 20:27:00 +0000 (16:27 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 25 Jun 2019 20:57:17 +0000 (16:57 -0400)
commitbdec440ecc0854529c60659683cd3acd4696fd1c
treeb5070e6c9d9e904668736615b875eae8295b1cc3tree | snapshot
parentdcdded9d153295c176053c245772a67eef222aa8commit | diff
Add retry to Music get calls

Add 3 retries to Music get calls.
Ideally, should allow configuration of number of retries.

Issue-ID: MUSIC-416
Signed-off-by: Martella, Arthur <arthur.martella.1@att.com>
Change-Id: Ibdbc8c91da103b8058e46f8995f54e349a41afbd
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicMixin.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.