This repository has been archived by the owner on Oct 22, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 35
log-cache NODE_INDEX incorrect not reference to bpm.yml when multi_az enabled. #1106
Labels
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/174568554 The labels on this github issue will be updated when the story is started. |
This should be fixed by https://www.pivotaltracker.com/story/show/174661471 |
Looks like this was never fixed. I added https://www.pivotaltracker.com/story/show/177062682 |
It does, but it is still possible that we'll have to change that in the future... It is only a singleton because of memory leak issues, but making it a singleton cause early expiration of logs, so it is not really a solution, even if you accept that |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
When deploy kubecf with multi_az=true, all the log-cache jobs started with
NODE_INDEX=0
and this cause the log-cache cluster not working properly.cf logs
not work.cf push xxx
andcf app xxx
not working, failed with client timeout.To Reproduce
cf-operator: 5.2.0
kubecf: v2.2.3
deploy kubecf with multi_az=true
config log-cache with more than 1 instance.
for example:
login log-cache container (take log-cache-z1-0 for example) and check the environment
NODE_INDEX
:check file /var/vcap/jobs/log-cache/config/bpm.yml,
check the log-cache logs
Check the statefulset log-cache in each zone:
NODE_INDEX is set as the Environment of container log-cache-log-cache
issue:
The log-cache job start reference to the container environment value
NODE_INDEX=0
instead of using the value in bpm.yml, and this cause all the log-cache jobs run withNODE_INDEX=0
and fail to work as a cluster.Expected behavior
logcach job can join the cluster with correct NODE_INDEX, the value in bpm.yml
Environment
cf-operator: 5.2.0
kubecf: v2.2.3
The text was updated successfully, but these errors were encountered: