10:37 a.m.
Branch: refs/heads/schema-installer
Home: https://github.com/hawkular/hawkular-metrics
Commit: 917c6d531dec174bdbb1b9883906a26be2165560
https://github.com/hawkular/hawkular-metrics/commit/917c6d531dec174bdbb1b...
Author: John Sanda <john.sanda(a)gmail.com>
Date: 2018-03-02 (Fri, 02 Mar 2018)
Changed paths:
A core/schema-installer/mylogback.xml
A core/schema-installer/pom.xml
A core/schema-installer/src/main/java/org/hawkular/metrics/schema/Installer.java
A core/schema-installer/src/main/resources/logback.xml
M core/schema/pom.xml
M core/schema/src/main/java/org/hawkular/metrics/schema/SchemaService.java
M pom.xml
Log Message:
-----------
[HWKMETRICS-756] initial commit for schema installer
The schema-installer module produces an executable, fat jar. The
installer is a wrapper around SchemaService which in turn runs Cassalog.
The installer does not assume that Cassandra is already running, but it
does assume that Cassandra will be running eventually. As such, if
connecting to C* fails, the installer will wait for 5 seconds and try
again. It will continue to do so until it establishes a connection.
Logback is used for logging. A logback.xml is embedded in the executable
jar. Logging will be sent to stdout by default at INFO level. The
logging configuration can be overriden by setting the
logback.configurationFile system property.
Commit: ab0e6690fd8b981d8c312f4cdd16a995f8d12201
https://github.com/hawkular/hawkular-metrics/commit/ab0e6690fd8b981d8c312...
Author: John Sanda <john.sanda(a)gmail.com>
Date: 2018-03-06 (Tue, 06 Mar 2018)
Changed paths:
M api/metrics-api-jaxrs/pom.xml
R
api/metrics-api-jaxrs/src/main/java/org/hawkular/metrics/api/jaxrs/DistributedLock.java
M
api/metrics-api-jaxrs/src/main/java/org/hawkular/metrics/api/jaxrs/MetricsServiceLifecycle.java
A
api/metrics-api-jaxrs/src/main/java/org/hawkular/metrics/api/jaxrs/util/SchemaChecker.java
R api/metrics-api-jaxrs/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
M core/metrics-core-service/pom.xml
M
core/metrics-core-service/src/main/java/org/hawkular/metrics/core/jobs/JobsService.java
M
core/metrics-core-service/src/main/java/org/hawkular/metrics/core/jobs/JobsServiceImpl.java
M
core/metrics-core-service/src/test/java/org/hawkular/metrics/core/jobs/CompressDataJobITest.java
M
core/metrics-core-service/src/test/java/org/hawkular/metrics/core/jobs/DeleteExpiredMetricsJobITest.java
M
core/metrics-core-service/src/test/java/org/hawkular/metrics/core/jobs/DeleteTenantITest.java
M
core/metrics-core-service/src/test/java/org/hawkular/metrics/core/service/BaseITest.java
M core/schema-installer/pom.xml
M core/schema-installer/src/main/java/org/hawkular/metrics/schema/Installer.java
M core/schema/src/main/java/org/hawkular/metrics/schema/SchemaService.java
A core/schema/src/main/java/org/hawkular/metrics/schema/VersionUpdateException.java
M core/schema/src/main/resources/org/hawkular/schema/cassalog.groovy
M
dist/containers/hawkular-metrics-openshift/src/main/webapp/WEB-INF/jboss-deployment-structure.xml
M job-scheduler/pom.xml
A job-scheduler/src/main/java/org/hawkular/metrics/scheduler/api/JobsManager.java
Log Message:
-----------
[HWKMETRICS-756] move schema updates to installer
The schema installer first runs SchemaService to apply schema updates. I
also put the code for creating background jobs into the installer as
well. There are some potential race conditions with creating those jobs,
which is why an infinispan cache was used for coordination. By moving
the job creation to the installer, there is no more concern about
multiple instances of the job creation code running concurrently.
Compare:
https://github.com/hawkular/hawkular-metrics/compare/917c6d531dec^...ab0e...