Netflix/Conductor prints too many dynomite related logs
up vote
1
down vote
favorite
I'm using Netflix/Conductor with docker-compose
. When I set the docker-compose.yml
file up I see too many lines related to dynomite. I think it consumes a lot of memory and slows down my system. I have to mention that Conductor doesn't use the official Netflix/Dynomite
image but it uses v1r3n/dynomite
image. Is there any way to reduce the amount of logs related to it? I know it's possible with grep to reduce logs, but I want to change the log level or use the official dynomite image. My current docker-file (by the way its the official version in Netflix/Conductor github repo):
# Docker compose for netflix conductor + elasticsearch + dynomite
version: '2'
services:
conductor-server:
environment:
- CONFIG_PROP=config.properties
image: conductor:server
build:
context: ../
dockerfile: docker/server/Dockerfile
ports:
- 8080:8080
links:
- elasticsearch:es
- dynomite:dyno1
conductor-ui:
environment:
- WF_SERVER=http://conductor-server:8080/api/
image: conductor:ui
build:
context: ../
dockerfile: docker/ui/Dockerfile
ports:
- 5000:5000
links:
- conductor-server
dynomite:
image: v1r3n/dynomite
elasticsearch:
image: elasticsearch:2.4
docker redis docker-compose netflix netflix-conductor
add a comment |
up vote
1
down vote
favorite
I'm using Netflix/Conductor with docker-compose
. When I set the docker-compose.yml
file up I see too many lines related to dynomite. I think it consumes a lot of memory and slows down my system. I have to mention that Conductor doesn't use the official Netflix/Dynomite
image but it uses v1r3n/dynomite
image. Is there any way to reduce the amount of logs related to it? I know it's possible with grep to reduce logs, but I want to change the log level or use the official dynomite image. My current docker-file (by the way its the official version in Netflix/Conductor github repo):
# Docker compose for netflix conductor + elasticsearch + dynomite
version: '2'
services:
conductor-server:
environment:
- CONFIG_PROP=config.properties
image: conductor:server
build:
context: ../
dockerfile: docker/server/Dockerfile
ports:
- 8080:8080
links:
- elasticsearch:es
- dynomite:dyno1
conductor-ui:
environment:
- WF_SERVER=http://conductor-server:8080/api/
image: conductor:ui
build:
context: ../
dockerfile: docker/ui/Dockerfile
ports:
- 5000:5000
links:
- conductor-server
dynomite:
image: v1r3n/dynomite
elasticsearch:
image: elasticsearch:2.4
docker redis docker-compose netflix netflix-conductor
I couldn't add a tag for netflix-dynomite or dynomite
– ksadjad
yesterday
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm using Netflix/Conductor with docker-compose
. When I set the docker-compose.yml
file up I see too many lines related to dynomite. I think it consumes a lot of memory and slows down my system. I have to mention that Conductor doesn't use the official Netflix/Dynomite
image but it uses v1r3n/dynomite
image. Is there any way to reduce the amount of logs related to it? I know it's possible with grep to reduce logs, but I want to change the log level or use the official dynomite image. My current docker-file (by the way its the official version in Netflix/Conductor github repo):
# Docker compose for netflix conductor + elasticsearch + dynomite
version: '2'
services:
conductor-server:
environment:
- CONFIG_PROP=config.properties
image: conductor:server
build:
context: ../
dockerfile: docker/server/Dockerfile
ports:
- 8080:8080
links:
- elasticsearch:es
- dynomite:dyno1
conductor-ui:
environment:
- WF_SERVER=http://conductor-server:8080/api/
image: conductor:ui
build:
context: ../
dockerfile: docker/ui/Dockerfile
ports:
- 5000:5000
links:
- conductor-server
dynomite:
image: v1r3n/dynomite
elasticsearch:
image: elasticsearch:2.4
docker redis docker-compose netflix netflix-conductor
I'm using Netflix/Conductor with docker-compose
. When I set the docker-compose.yml
file up I see too many lines related to dynomite. I think it consumes a lot of memory and slows down my system. I have to mention that Conductor doesn't use the official Netflix/Dynomite
image but it uses v1r3n/dynomite
image. Is there any way to reduce the amount of logs related to it? I know it's possible with grep to reduce logs, but I want to change the log level or use the official dynomite image. My current docker-file (by the way its the official version in Netflix/Conductor github repo):
# Docker compose for netflix conductor + elasticsearch + dynomite
version: '2'
services:
conductor-server:
environment:
- CONFIG_PROP=config.properties
image: conductor:server
build:
context: ../
dockerfile: docker/server/Dockerfile
ports:
- 8080:8080
links:
- elasticsearch:es
- dynomite:dyno1
conductor-ui:
environment:
- WF_SERVER=http://conductor-server:8080/api/
image: conductor:ui
build:
context: ../
dockerfile: docker/ui/Dockerfile
ports:
- 5000:5000
links:
- conductor-server
dynomite:
image: v1r3n/dynomite
elasticsearch:
image: elasticsearch:2.4
docker redis docker-compose netflix netflix-conductor
docker redis docker-compose netflix netflix-conductor
edited yesterday
asked yesterday
ksadjad
1729
1729
I couldn't add a tag for netflix-dynomite or dynomite
– ksadjad
yesterday
add a comment |
I couldn't add a tag for netflix-dynomite or dynomite
– ksadjad
yesterday
I couldn't add a tag for netflix-dynomite or dynomite
– ksadjad
yesterday
I couldn't add a tag for netflix-dynomite or dynomite
– ksadjad
yesterday
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
you can expose stats/admin port 22222:
dynomite:
image: v1r3n/dynomite
ports:
- 22222:22222
and after that use admin api to decrease or increase log level and so on ( as described in https://github.com/Netflix/dynomite/wiki/REST )
to decrease log level following API muse be called :
curl -s http://localhost:22222/logleveldown
1
This works! But I still need to manually do this. Is there a way to decrease the log while I'm setting thedocker-compose.yml
file up?
– ksadjad
22 hours ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
you can expose stats/admin port 22222:
dynomite:
image: v1r3n/dynomite
ports:
- 22222:22222
and after that use admin api to decrease or increase log level and so on ( as described in https://github.com/Netflix/dynomite/wiki/REST )
to decrease log level following API muse be called :
curl -s http://localhost:22222/logleveldown
1
This works! But I still need to manually do this. Is there a way to decrease the log while I'm setting thedocker-compose.yml
file up?
– ksadjad
22 hours ago
add a comment |
up vote
1
down vote
accepted
you can expose stats/admin port 22222:
dynomite:
image: v1r3n/dynomite
ports:
- 22222:22222
and after that use admin api to decrease or increase log level and so on ( as described in https://github.com/Netflix/dynomite/wiki/REST )
to decrease log level following API muse be called :
curl -s http://localhost:22222/logleveldown
1
This works! But I still need to manually do this. Is there a way to decrease the log while I'm setting thedocker-compose.yml
file up?
– ksadjad
22 hours ago
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
you can expose stats/admin port 22222:
dynomite:
image: v1r3n/dynomite
ports:
- 22222:22222
and after that use admin api to decrease or increase log level and so on ( as described in https://github.com/Netflix/dynomite/wiki/REST )
to decrease log level following API muse be called :
curl -s http://localhost:22222/logleveldown
you can expose stats/admin port 22222:
dynomite:
image: v1r3n/dynomite
ports:
- 22222:22222
and after that use admin api to decrease or increase log level and so on ( as described in https://github.com/Netflix/dynomite/wiki/REST )
to decrease log level following API muse be called :
curl -s http://localhost:22222/logleveldown
answered 22 hours ago
Farid327
485
485
1
This works! But I still need to manually do this. Is there a way to decrease the log while I'm setting thedocker-compose.yml
file up?
– ksadjad
22 hours ago
add a comment |
1
This works! But I still need to manually do this. Is there a way to decrease the log while I'm setting thedocker-compose.yml
file up?
– ksadjad
22 hours ago
1
1
This works! But I still need to manually do this. Is there a way to decrease the log while I'm setting the
docker-compose.yml
file up?– ksadjad
22 hours ago
This works! But I still need to manually do this. Is there a way to decrease the log while I'm setting the
docker-compose.yml
file up?– ksadjad
22 hours ago
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53238060%2fnetflix-conductor-prints-too-many-dynomite-related-logs%23new-answer', 'question_page');
}
);
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I couldn't add a tag for netflix-dynomite or dynomite
– ksadjad
yesterday