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

Block Lag #4

Closed
proletesseract opened this issue Jan 26, 2017 · 2 comments
Closed

Block Lag #4

proletesseract opened this issue Jan 26, 2017 · 2 comments

Comments

@proletesseract
Copy link
Member

proletesseract commented Jan 26, 2017 •
edited
Loading

Look to increase the private settings for blockThreshold.processing to 2 blocks and assess stability.

Also, only send email if the hanging daemon catch is executed or the daemon is more than blockThreshold.checking blocks behind.
@proletesseract
Copy link
Member Author

{"success":false,"data":{"message":"navClient block check failed"}}

@proletesseract
Copy link
Member Author

block lag lenience increased to 3/5 blocks

proletesseract added a commit that referenced this issue Mar 30, 2017
@proletesseract
Merge branch '#4-navtech-1.1' into #14-return-all-to-senders
912da04
proletesseract added a commit that referenced this issue Mar 31, 2017
@proletesseract
Merge pull request #22 from navcoindev/#4-navtech-1.1
1acdc59 
#4 navtech 1.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@proletesseract