linkedin / linkedin/Burrow

Burrow process crashed

Open
#511 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
4k
Forks
818
Avg merge
1h 14m
Merged PRs (30d)
1

Description

Burrow is crashing after certain time, without showing any information other than some fatal memory error.

Below is the config file. (removed server names from the file)

[general]
pidfile="burrow.pid"
stdout-logfile="burrow.out"
access-control-allow-origin="*"

[logging]
filename="logs/burrow.log"
level="info"
maxsize=100
maxbackups=30
maxage=10
use-localtime=false
use-compression=true

[zookeeper]
servers=[ "" ]
timeout=6
zookeeper-offsets=true

[cluster.dev_cluster]
client-profile="dev_cluster"
class-name="kafka"
servers=[ "" ]
topic-refresh=120
offset-refresh=30
offset-topic="__consumer_offsets"

[storage.default]
class-name="inmemory"
workers=20
intervals=15
expire-group=604800
min-distance=1

[client-profile.dev_cluster]
client-id="burrow-client"
kafka-version="0.11.0"

[consumer.consumer_dev_cluster_kafka]
class-name="kafka"
cluster="dev_cluster"
servers=[ "" ]
client-profile="dev_cluster"
group-blacklist="^(console-consumer-|python-kafka-consumer-|quick-).*$"
group-whitelist=""

[consumer.consumer_dev_cluster_zk]
class-name="kafka_zk"
cluster="dev_cluster"
servers=[ "" ]
zookeeper-timeout=30
group-blacklist="^(console-consumer-|python-kafka-consumer-).*$"

[httpserver.default]
address=":8050"

Logs are attached
[burrow.txt](https://github.com/linkedin/Burrow/files/3005235/burrow.txt)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the attached burrow.txt log and comparing the supplied configuration, especially the storage and Kafka/Zookeeper settings. Reproduce the crash with that configuration if possible; done means identifying the memory-error cause and documenting or fixing it with a regression check, though the payload names no source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kafka
Domain
observability
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.