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 starvation and busy waiting of ES IndexerBolt #989

Merged
merged 2 commits into from
Jul 12, 2022

Conversation

FelixEngl
Copy link
Contributor

@FelixEngl FelixEngl commented Jul 8, 2022

The IndexerBold has the same problems as StatusUpdaterBold.
Basically copy-pasted the StatusUpdaterBold into IndexerBold and changed some status handling code. (see #988)

When the parent PR is accepted this one will only differ in 2 files. (Parent PR: #988)

Best Regards
Felix

Signed-off-by: Felix Engl felix.engl@uni-bamberg.de

Thanks for contributing to StormCrawler, your efforts are appreciated!

Developer Certificate of Origin

By contributing to StormCrawler, you accept and agree to the following terms and conditions (the Developer Certificate of Origin) for your present and future contributions submitted to StormCrawler.
Please refer to the Developer Certificate of Origin section in CONTRIBUTING.md for details.

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Before opening a PR, please check that:

  • You've squashed your commits into a single one
  • You've described what the PR does or at least point to a related issue
  • You've signed-ff your commits with 'git commit -s'
  • The code is properly formatted with 'mvn git-code-format:format-code -Dgcf.globPattern=**/*'

Thanks!

Protect BulkInsert from accidential closure, fix errors in close.

Signed-off-by: Felix Engl <felix.engl@uni-bamberg.de>
@jnioche jnioche changed the title Fix starvation and busy waiting of ES IndexerBold Fix starvation and busy waiting of ES IndexerBolt Jul 11, 2022
@jnioche
Copy link
Contributor

jnioche commented Jul 11, 2022

can you please rebase this PR against the main branch? It will be easier to review

@jnioche jnioche merged commit c33a181 into apache:master Jul 12, 2022
@jnioche
Copy link
Contributor

jnioche commented Jul 12, 2022

Thanks @FelixEngl


if (bulkItemsWithFailedFlag.size() == 1) {
selected = bulkItemsWithFailedFlag.get(0);
} else {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Please review the following lines (328 - 344), in the original code we processed all BulkResponseItems. Here we abbreviate that and only process the first fail or the last ack.
Does this comply with the wanted behaviour or do we want to process all?
We could also just increase the counts like we are processing all of them but in the end we only process it once. (By increasing the counts and the the reports by the length of bulkItemsWithFailedFlag in line 329)

Copy link
Contributor

Choose a reason for hiding this comment

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

I missed this bit. we need to process all BulkResponseItems as in the original

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Reopen this PR oder making a new one fixing this mistake?

@FelixEngl
Copy link
Contributor Author

FelixEngl commented Jul 12, 2022

@jnioche
I forgot to submit my review request. 🤦
This came to me early in the morning and I forgot to submit it.

Sorry for that. (I don't think It'll mess up any logic except counting acks and failures, so there won't be any problem with the crawling itself.)

@jnioche
Copy link
Contributor

jnioche commented Jul 12, 2022 via email

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

Successfully merging this pull request may close these issues.

None yet

2 participants