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

fix kafka hostname #172

Merged
merged 1 commit into from
Aug 13, 2020
Merged

fix kafka hostname #172

merged 1 commit into from
Aug 13, 2020

Conversation

thiagodpf
Copy link
Contributor

@thiagodpf thiagodpf commented Aug 13, 2020

  • Please check if the PR fulfills these requirements
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

bug fix

  • What is the current behavior? (You can also link to an open issue here)

When the kafka container is destroyed and a new container is created, the host name changes and this causes the V2K to not be able to take mqtt messages from verne to kafka.

  • What is the new behavior (if this is a feature change)?

When the kafka container is destroyed and a new container is created, the host name must be the same.

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

no

  • Is there any issue related to this PR in other repository? (such as dojot/dojot)

This problem started to occur after the volumes were mapped on the docker-compose:
dojot/dojot#1585
dojot/dojot#1484

  • Other information:

@thiagodpf thiagodpf self-assigned this Aug 13, 2020
Copy link
Contributor

@rascaraficci rascaraficci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks OK!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants