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

Feature: FCC node directory is queried on every plan execution #1243

Conversation

paullatzelsperger
Copy link
Member

@paullatzelsperger paullatzelsperger commented May 2, 2022

What this PR changes/adds

On every crawler run that the PartitionManagerImpl schedules, the FederatedCacheNodeDirectory is queried to get up-to-date information about "who is in the dataspace".

Note the periodic scheduling is implemented in the ExecutionPlan, or more specifically the RecurringExecutionPlan. This is because crawlers themselves are not scheduled in any form, they merely activate when a new WorkItem arrives in their queue.

Why it does that

To be able to react to changes in the node directory

Further notes

  • completely unrelated: the port in the http provisioner test was randomized, because I noticed that that test fails when the port is already bound.

Linked Issue(s)

Closes #1230

Checklist

  • added appropriate tests?
  • performed checkstyle check locally?
  • added/updated copyright headers?
  • documented public classes/methods?
  • added/updated relevant documentation?
  • added relevant details to the changelog? (skip with label no-changelog)
  • formatted title correctly? (take a look at the CONTRIBUTING and styleguide for details)

@codecov-commenter
Copy link

codecov-commenter commented May 2, 2022

Codecov Report

Merging #1243 (4fbcf23) into main (0da15e1) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #1243      +/-   ##
============================================
- Coverage     59.37%   59.36%   -0.02%     
+ Complexity     2837     2835       -2     
============================================
  Files           712      712              
  Lines         15689    15689              
  Branches       1037     1037              
============================================
- Hits           9315     9313       -2     
- Misses         5954     5956       +2     
  Partials        420      420              
Impacted Files Coverage Δ
.../catalog/cache/FederatedCatalogCacheExtension.java 80.32% <ø> (-1.64%) ⬇️
...catalog/cache/management/PartitionManagerImpl.java 86.66% <100.00%> (ø)
...ector/catalog/directory/InMemoryNodeDirectory.java 40.00% <0.00%> (-20.00%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0da15e1...4fbcf23. Read the comment docs.

…clipse/dataspaceconnector/catalog/cache/management/PartitionManagerImpl.java

Co-authored-by: Alexandre Gattiker <[email protected]>
@bscholtes1A bscholtes1A merged commit 434e4aa into eclipse-edc:main May 3, 2022
algattik added a commit to agera-edc/DataSpaceConnector that referenced this pull request May 3, 2022
…se-edc#1243)

* node directory is queried on every plan execution

* checkstyle

* Update extensions/catalog/federated-catalog-cache/src/main/java/org/eclipse/dataspaceconnector/catalog/cache/management/PartitionManagerImpl.java

Co-authored-by: Alexandre Gattiker <[email protected]>

Co-authored-by: Alexandre Gattiker <[email protected]>
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.

Federated Catalog: the FCN directory should be updated periodically
4 participants