linkedin / linkedin/Burrow

Burrow failing on starting

Open
#670 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

The pod is in the "CrashLoopBackOff" state, in the log i see this output:
Reading configuration from /etc/burrow ││ {"level":"info","ts":1605889227.219109,"msg":"Started Burrow"} ││ {"level":"info","ts":1605889227.2191644,"msg":"configuring","type":"coordinator","name":"zookeeper"} ││ {"level":"info","ts":1605889227.2196777,"msg":"configuring","type":"coordinator","name":"storage"} ││ {"level":"info","ts":1605889227.2196999,"msg":"configuring","type":"module","coordinator":"storage","class":"inmemory","name":"default"} ││ {"level":"info","ts":1605889227.219759,"msg":"configuring","type":"coordinator","name":"evaluator"} ││ {"level":"info","ts":1605889227.2197745,"msg":"configuring","type":"module","coordinator":"evaluator","class":"caching","name":"default"} ││ {"level":"info","ts":1605889227.219791,"msg":"configuring","type":"coordinator","name":"httpserver"} ││ {"level":"info","ts":1605889227.2199345,"msg":"configuring","type":"coordinator","name":"notifier"} ││ {"level":"info","ts":1605889227.2199461,"msg":"configuring","type":"coordinator","name":"cluster"} ││ {"level":"info","ts":1605889227.2199554,"msg":"configuring","type":"module","coordinator":"cluster","class":"kafka","name":"monet"} ││ {"level":"info","ts":1605889227.220327,"msg":"configuring","type":"coordinator","name":"consumer"} ││ {"level":"info","ts":1605889227.2203572,"msg":"configuring","type":"module","coordinator":"consumer","class":"kafka_zk","name":"monet_zk"} ││ {"level":"panic","ts":1605889227.2208025,"msg":"Please change configurations to allowlist and denylist","type":"module","coordinator":"consumer","class":"kafka_zk","name":"monet_zk"} ││ {"level":"panic","ts":1605889227.2208335,"msg":"Please change configurations to allowlist and denylist"} ││ panic: Please change configurations to allowlist and denylist [recovered] ││ panic: Please change configurations to allowlist and denylist [recovered] ││ panic: Please change configurations to allowlist and denylist ││ goroutine 1 [running]: ││ main.handleExit()

I have no chance to enter the pod, do you have any advice?

panic: Please change configurations to allowlist and denylist [recovered] -> what does it refer to?

Thanks!!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the startup log and the Burrow configuration for the consumer module using class kafka_zk. Compare its settings with the allowlist and denylist requirement, then reproduce the CrashLoopBackOff behavior. Done means identifying the configuration change or confirmed fix that allows the pod to start.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
backend, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.