Skip to content
This repository was archived by the owner on Aug 23, 2020. It is now read-only.

Refactor: Removed grace time from solid entry points generation#1199

Merged
GalRogozinski merged 2 commits intoiotaledger-archive:dev-localsnapshotsfrom
iotadevelopment:merge_removegracetime
Nov 29, 2018
Merged

Refactor: Removed grace time from solid entry points generation#1199
GalRogozinski merged 2 commits intoiotaledger-archive:dev-localsnapshotsfrom
iotadevelopment:merge_removegracetime

Conversation

@hmoog
Copy link
Copy Markdown

@hmoog hmoog commented Nov 28, 2018

Description

This PR removes the grace time from the solid entry points generation. It was added in the past to work around the back referencing transaction issue. Since the issue can not be solved by just keeping the solid entry points alive for a little longer time and needs to be addressed separately (we will use cuckoo filters for this later on), it can and should be removed.

Especially in scenarios where we have a lot of TPS and a side tangle (like it happened today) it can slow the snapshot generation noticable and disrupt the operation of the node.

Note: This PR also changes the info message when the sendqueue is full to being a debug message because it can otherwise spam the CLI output making it very hard to debug problems and see important messages of the console output.

Type of change

  • Bug fix (a non-breaking change which fixes an issue)

Checklist:

  • My code follows the style guidelines for this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • New and existing unit tests pass locally with my changes

@hmoog hmoog changed the title Refactor: removed grace time Refactor: Removed grace time from solid entry points generation Nov 28, 2018
if (sendQueue.remainingCapacity() == 0) {
sendQueue.poll();
log.info("Sendqueue full...dropped 1 tx");
log.debug("Sendqueue full...dropped 1 tx");
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I found this info statement very useful while trying to peer nodes and noticing right away that there is a problem.
I agree it is very annoying the way it can flood the console.

Maybe use the IntervalLogger?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

We already have the connection message for this case. In case a node drops the connection or doesnt accept packets (like with NELSON) you will not see anything in your cli.

@GalRogozinski
Copy link
Copy Markdown
Contributor

Since the issue can not be solved by just keeping the solid entry points alive for a little longer time and needs to be addressed separately (we will use cuckoo filters for this later on), it can and should be removed

Maybe we do this change when we start applying the cuckoo filter?

@GalRogozinski GalRogozinski merged commit 433d26a into iotaledger-archive:dev-localsnapshots Nov 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants