Skip to content
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

Kafka won't start after update #1009

Closed
adam1010 opened this issue Jun 28, 2021 · 6 comments · Fixed by #1021
Closed

Kafka won't start after update #1009

adam1010 opened this issue Jun 28, 2021 · 6 comments · Fixed by #1021
Assignees
Labels
release-blocker Any issue open with this tag will stop CalVer releases from happening

Comments

@adam1010
Copy link

Version Information

Version: Sentry 21.7.0.dev0ee22e17

Steps to Reproduce

  1. I use Docker. I was on a relatively recent version. used the ./install.sh script to upgrade
  2. It won't start up at all anymore.

Is there a way to at least recover so I can login to look at my assigned tickets? (even if I need to rollback?)

Actual Result

image

image

image

What actually happened. Maybe a screenshot/recording?

Logs

image
image

@adam1010
Copy link
Author

@BYK I'm available on Sentry Discord if you want me to share my screen or let you look through logs

@BYK
Copy link
Member

BYK commented Jun 29, 2021

@adam1010 we recently upgraded Kafka and Zookeeper in #1002. This might be related. Can you try reverting those two to 5.5.0 and try that way?

@djbe
Copy link

djbe commented Jun 29, 2021

I can confirm that reverting those 2 lines in the docker-compose.yml (and running ./install.sh) fixes the issue.

@BYK BYK added release-blocker Any issue open with this tag will stop CalVer releases from happening Status: In Progress labels Jun 29, 2021
@BYK BYK self-assigned this Jun 29, 2021
@BYK
Copy link
Member

BYK commented Jun 29, 2021

Looks like the Kafka upgrade was not smooth. I'll dig into this.

@adam1010
Copy link
Author

Confirmed, rolling back to cp-zookeeper:5.5.0 in the two locations in docker-compose.yml then using ./install.sh got me back up and running. Thank you!

Not sure if this is helpful, but the first time I ran ./install.sh I had not done a git pull on the repo. If that's an important part of the process, you might consider adding a git pull command to the beginning of the ./install.sh script to force it.

@BYK BYK reopened this Jun 29, 2021
@BYK
Copy link
Member

BYK commented Jun 29, 2021

@adam1010 if you are on the nightly builds, we expect you to pull the latest version of this repo too. If you are using the tagged CalVer releases, then you already should be using a tagged version of this repo 🙂

Keeping the issue open as master is still problematic for upgrades I think.

BYK added a commit that referenced this issue Jul 2, 2021
Fixes #1009 by partially reverting #1002. We need to make a 21.6.2 release soon and I didn't have time to dig into why Kafka upgrades were failing so reverting for safety for now.
@BYK BYK closed this as completed in #1021 Jul 2, 2021
BYK added a commit that referenced this issue Jul 2, 2021
Fixes #1009 by partially reverting #1002. We need to make a 21.6.2 release soon and I didn't have time to dig into why Kafka upgrades were failing so reverting for safety for now.
@github-actions github-actions bot locked and limited conversation to collaborators Jul 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-blocker Any issue open with this tag will stop CalVer releases from happening
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants