Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: ef6c1fd) | patch
Disable Range-reuse to avoid Connection Pooling Issues 93/91693/2
authorstatta <statta@research.att.com>
Thu, 18 Jul 2019 19:18:59 +0000 (15:18 -0400)
committerstatta <statta@research.att.com>
Thu, 18 Jul 2019 19:26:01 +0000 (15:26 -0400)
commit37f5ca0aa6f950b77da6acbeed5c9ae7069c3d6e
treed55f0be668ed8cef1d89fdd22083339e7bce5730tree | snapshot
parentef6c1fdb836b7ecb79d9ff1cd29b7c5debe1a7f8commit | diff
Disable Range-reuse to avoid Connection Pooling Issues

Issue-ID: MUSIC-435
Change-Id: I7a1abfc7b107022869be76d33157999b139d761c
Signed-off-by: statta <statta@research.att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/StateManager.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/tools/TxDigestDecompression.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.