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.

Sign up for GitHub

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

Jump to bottom

Epoch duration extends if IR is restarted near expected epoch tick time #3007

Open
carpawell opened this issue Nov 11, 2024 · 0 comments
Open

Epoch duration extends if IR is restarted near expected epoch tick time #3007

carpawell opened this issue Nov 11, 2024 · 0 comments
Labels
bug Something isn't working I4 No visible changes neofs-ir Inner Ring node application issues S4 Routine U4 Nothing urgent
Milestone
v0.45.0

Comments

@carpawell
Copy link
Member

carpawell commented Nov 11, 2024 •
edited
Loading

Is your feature request related to a problem? Please describe.

I'm always frustrated when epoch lasts longer than 240 blocks in our networks.

Describe the solution you'd like

If IR is restarted, it should be possible to vote correctly for a new epoch tick. There should not be situations when we waiting for new block timers to tick or when multisignature voting fails.

Describe alternatives you've considered

Wake up, see the actual epoch status, vote (if not yet) based on the last epoch tick block.

Additional context

11.11.2024, mainnet
image
@carpawell carpawell added enhancement Improving existing functionality neofs-ir Inner Ring node application issues labels Nov 11, 2024
@roman-khimov roman-khimov added bug Something isn't working U4 Nothing urgent S4 Routine I4 No visible changes and removed enhancement Improving existing functionality labels Nov 11, 2024
@roman-khimov roman-khimov added this to the v0.45.0 milestone Nov 11, 2024
@carpawell carpawell mentioned this issue Dec 4, 2024
Closed
carpawell added a commit that referenced this issue Dec 6, 2024
@carpawell
morph: increase buffer for notification handling routines
4bbeefd 
10 is too low value for practice. It is not mind-blowing to receive tens of
notifications per block and, moreover, it was already seen in real networks.
Refs #3007.

Signed-off-by: Pavel Karpy <[email protected]>
carpawell added a commit that referenced this issue Dec 6, 2024
@carpawell
morph: increase buffer for notification handling routines
6b648df 
10 is too low value for practice. It is not mind-blowing to receive tens of
notifications per block and, moreover, it was already seen in real networks.
Refs #3007.

Signed-off-by: Pavel Karpy <[email protected]>
carpawell added a commit that referenced this issue Dec 6, 2024
@carpawell
morph: increase buffer for notification handling routines
19c72bf 
10 is too low value for practice. It is not mind-blowing to receive tens of
notifications per block and, moreover, it was already seen in real networks.
Refs #3007.

Signed-off-by: Pavel Karpy <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working I4 No visible changes neofs-ir Inner Ring node application issues S4 Routine U4 Nothing urgent
Projects
None yet
Milestone
v0.45.0
Development

No branches or pull requests
2 participants
@roman-khimov @carpawell