Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
T
theodolite
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Analyze
Contributor analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sören Henning
theodolite
Commits
fef26208
Commit
fef26208
authored
3 years ago
by
Sören Henning
Browse files
Options
Downloads
Patches
Plain Diff
Add starting docs for docker tests
parent
b9e21dea
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
theodolite-benchmarks/docker-test/README.md
+38
-0
38 additions, 0 deletions
theodolite-benchmarks/docker-test/README.md
with
38 additions
and
0 deletions
theodolite-benchmarks/docker-test/README.md
0 → 100644
+
38
−
0
View file @
fef26208
# Docker Compose Files for Testing
This directory contains Docker Compose files, which help testing Benchmark implementations.
For each stream processing engine (Kafka Streams and Flink) and Benchmark (UC1-4), a Docker Compose file is provided
in the corresponding subdirectory.
## Full Dockerized Testing
Running the load generator, the benchmark and all required infrastructure (Kafka etc.) is easy. Simply,
`cd`
into the
directory of the benchmark implementation Compose file and
*up*
it.
For example:
```
sh
cd
uc1-kstreams-docker-compose/
docker-compose up
-d
```
On less powerful hardware, starting all containers together might fail. In such cases, it usually helps to first
*up*
Kafka and ZooKeeper (
`docker-compose up -d kafka zookeeper`
), then after some delay the Schema Registry
(
`docker-compose up -d schema-registry`
) and finally, after some more further delay, the rest (
`docker-compose up -d`
).
To tear down the entire Docker Compose configuration:
```
sh
docker-compose down
```
## Benchmark (+ Load Generator) on Host, Infrastructure in Docker
For development and debugging purposes, it is often required to run the benchmark and/or the load generator directly on
the host, for example, from the IDE or Gradle. In such cases, the following adjustments have to be made to the
`docker-compose.yaml`
file:
1.
Comment out the services that you intend to run locally.
2.
Uncomment the
`ports`
block in the Kafka and the Schema Registry services.
You can now connect to Kafka from your host system with bootstrap server
`localhost:19092`
and contact the Schema
Registry via
`localhost:8081`
.
**
Pay attention to the Kafka port, which is
*19092*
instead of the default one
*9092*
.
**
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment