-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
memberlist advertise_addr not used when advertising node address #9887
Comments
I expect this is somewhat related to #5610 |
Changing the loki.yml to the following seems to work somewhat, now it successfully starts but ends up with "too many unhealthy instances in the ring" auth_enabled: false
server:
http_listen_port: 3100
grpc_listen_port: 9096
common:
ring:
kvstore:
store: memberlist
instance_addr: ${ADVERTISE_ADDR}
replication_factor: 1
ingester:
wal:
enabled: true
dir: /tmp/wal
lifecycler:
final_sleep: 0s
memberlist:
abort_if_cluster_join_fails: false
join_members:
- ${MEMBERLIST_MEMBER}
advertise_addr: ${ADVERTISE_ADDR}
schema_config:
configs:
- from: 2020-10-24
store: boltdb-shipper
object_store: s3
schema: v11
index:
prefix: index_
period: 24h
storage_config:
boltdb_shipper:
active_index_directory: /loki/index
cache_location: /loki/index_cache
shared_store: s3
aws:
s3: http://${LOKI_USER}:${LOKI_PASSWORD}@${S3_URL}/${LOKI_BUCKET}
s3forcepathstyle: true
compactor:
working_directory: /loki/boltdb-shipper-compactor
shared_store: aws |
I have still problems with my configuration but they do not seem to be related with how this bug is formulated |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Trying to connect two loki nodes, each running on separate docker networks, to a memberlist fails. This seems to be as they do not use the advertise_addr when advertising their address.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The memberlist should be working
Environment:
Screenshots, Promtail config, or terminal output
loki.yml
docker-compose.yml - MEMBERLIST_MEMBER and ADVERTISE_ADDR are different on the two nodes
Relevant logs from one node
Full log from same node
The text was updated successfully, but these errors were encountered: