Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: c913f42) | patch
CreateNodeConfigurations never exits 49/73949/5
authorRob Daugherty <rd472p@att.com>
Thu, 29 Nov 2018 15:02:08 +0000 (10:02 -0500)
committerRob Daugherty <rd472p@att.com>
Tue, 4 Dec 2018 17:41:22 +0000 (17:41 +0000)
commit6703275b1697bd20cc0345a1292314bc4694bfde
treeaad2456e6a8373fc6f1ae80b1dd5fd77285f5232tree | snapshot
parentc913f4200caf3d2b0721bc3537112eb4d055b291commit | diff
CreateNodeConfigurations never exits

A non-daemon background thread is keeping the process alive
even when the main method is done.

Change-Id: I707a30df758e847a160f55512219add37eddaab1
Issue-ID: MUSIC-217
Signed-off-by: Rob Daugherty <rd472p@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/tools/CreateNodeConfigurations.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.