Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Multitenant configuration (2 tenants, 1 instance for every DI module, 1 partition for every DI topic):


moduleconfiguration
mod-data-import

mod-data-import-2.8.0-SNAPSHOT.260

name: DB_MAXPOOLSIZE value: '5'

name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties

SRMmod-source-record-manager

mod-source-record-manager-3.7.0-SNAPSHOT.762

name: DB_MAXPOOLSIZE value: '15'

name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties

name: DB_RECONNECTINTERVAL value: '1000'

name: DB_RECONNECTATTEMPTS value: '3'

SRSmod-source-record-storagemod-source-record-storage-5.6.3-SNAPSHOT.608594f
name: DB_MAXPOOLSIZE value: '15'
name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties
mod-inventory

mod-inventory-20.1.0-SNAPSHOT.607

name: DB_MAXPOOLSIZE value: '5'

name: JAVA_OPTIONS -XX:MaxRAMPercentage=85.0 -Dorg.folio.metadata.inventory.storage.type=okapi

mod-inventory-storage

mod-inventory-storage-26.0.0

 name: DB_MAXPOOLSIZE value: '5'

name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0

mod-di-converter-storage

mod-di-converter-storage-2.1.0-SNAPSHOT.9

name: DB_MAXPOOLSIZE value: '5'

name: JAVA_OPTIONS -XX:MaxRAMPercentage=66.0 -Djava.util.logging.config.file=vertx-default-jul-logging.properties

...

Its described in

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRMB-655
and
Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyRANCHER-621
(how we can use it by JMX and Prometheus in Gafana).

I created a task to deeply investigate the work of DI, its performance, and its use of resources:

Jira Legacy
serverSystem JiraJIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId01505d01-b853-3c2e-90f1-ee9b165564fc
keyMODSOURMAN-980

...