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

Correctly detect if Epoll is available #6256

Merged
merged 1 commit into from Feb 5, 2021
Merged

Conversation

npepinpe
Copy link
Member

@npepinpe npepinpe commented Feb 4, 2021

Description

This PR fixes Epoll detection in NettyMessagingService, which prevents the broker from running correctly on non-Linux OSes. There are no automated tests as we don't have the infrastructure to run tests on multiple platforms.

Related issues

closes #6247

Definition of Done

Not all items need to be done depending on the issue and the pull request.

Code changes:

  • The changes are backwards compatibility with previous versions
  • If it fixes a bug then PRs are created to backport the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. backport stable/0.25) to the PR, in case that fails you need to create backports manually.

Testing:

  • There are unit/integration tests that verify all acceptance criterias of the issue
  • New tests are written to ensure backwards compatibility with further versions
  • The behavior is tested manually
  • The change has been verified by a QA run
  • The impact of the changes is verified by a benchmark

Documentation:

  • The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
  • New content is added to the release announcement

@npepinpe
Copy link
Member Author

npepinpe commented Feb 4, 2021

This was broken on the 14th, so after the 0.26 release, so nothing to backport.

@npepinpe
Copy link
Member Author

npepinpe commented Feb 4, 2021

@korthout and @pihme can you quickly confirm the broker starts correctly on Mac and Windows? Thanks!

@korthout
Copy link
Member

korthout commented Feb 4, 2021

@npepinpe verified problem and fix on macOS

git fetch
git checkout 6247-netty-transport-fix
git checkout head^
mvn clean install
./dist/target/zeebe-broker/bin/broker
ERROR
git checkout -
mvn clean install
./dist/target/zeebe-broker/bin/broker
SUCCESS

Copy link
Contributor

@pihme pihme left a comment

Choose a reason for hiding this comment

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

Starts and shuts down properly on Windows.

Copy link
Contributor

@deepthidevaki deepthidevaki left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@npepinpe
Copy link
Member Author

npepinpe commented Feb 5, 2021

bors r+

@zeebe-bors
Copy link
Contributor

zeebe-bors bot commented Feb 5, 2021

Build succeeded:

@zeebe-bors zeebe-bors bot merged commit ea94092 into develop Feb 5, 2021
@zeebe-bors zeebe-bors bot deleted the 6247-netty-transport-fix branch February 5, 2021 08:43
@npepinpe
Copy link
Member Author

So my mistake, this needs to be backported because whatever broke it on the 14th, was then later backported to the 0.26 branch.

@npepinpe npepinpe mentioned this pull request Feb 22, 2021
9 tasks
zeebe-bors bot added a commit that referenced this pull request Feb 23, 2021
6411: Correctly detect Epoll r=saig0 a=npepinpe

## Description

This PR backports #6256 to stable/0.26. No merge conflicts or anything occurred.

## Related issues

closes #6247 

## Definition of Done

_Not all items need to be done depending on the issue and the pull request._

Code changes:
* [x] The changes are backwards compatibility with previous versions
* [ ] If it fixes a bug then PRs are created to [backport](https://github.com/zeebe-io/zeebe/compare/stable/0.24...develop?expand=1&template=backport_template.md&title=[Backport%200.24]) the fix to the last two minor versions. You can trigger a backport by assigning labels (e.g. `backport stable/0.25`) to the PR, in case that fails you need to create backports manually.

Testing:
* [x] There are unit/integration tests that verify all acceptance criterias of the issue
* [ ] New tests are written to ensure backwards compatibility with further versions
* [ ] The behavior is tested manually
* [ ] The change has been verified by a QA run
* [ ] The impact of the changes is verified by a benchmark 

Documentation: 
* [ ] The documentation is updated (e.g. BPMN reference, configuration, examples, get-started guides, etc.)
* [ ] New content is added to the [release announcement](https://drive.google.com/drive/u/0/folders/1DTIeswnEEq-NggJ25rm2BsDjcCQpDape)


Co-authored-by: Nicolas Pépin-Perreault <nicolas.pepin-perreault@camunda.com>
github-merge-queue bot pushed a commit that referenced this pull request Mar 14, 2024
…to use only position and partition for import (#6256)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Can't build executable broker on Mac OS
4 participants