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

BOSCore v3.0.1-rc2 LIB不走 #120

Closed
fufesou opened this issue Aug 1, 2019 · 9 comments
Closed

BOSCore v3.0.1-rc2 LIB不走 #120

fufesou opened this issue Aug 1, 2019 · 9 comments

Comments

@fufesou
Copy link

fufesou commented Aug 1, 2019 •
edited
Loading

5个BP节点，每个节点出12个块。
出现3次，30秒内lib不走，高度差达到60~76。期间head正常走，节点都在。
然后恢复正常。

image

这个是bug吗？如果不是，可以修改哪个配置，减少这种情况呢？
@oldcold
Copy link

oldcold commented Aug 2, 2019

This lib stuck indicated that your chain was under a view change, which is by design. This mechanism is employed to ensure liveness against faulty leaders, temporary network partition, etc. (Please refer to the original pbft algorithm here)

The view change comes with a timeout (which in the current version is 30 secs), nodes will enter the new view subsequently. To reduce the frequency of view changes, it is suggested to 1) keep all your nodes connected with each other, 2) adjust the overload of trxns to a level that fits your machine and 3) slightly increase the size of your bp schedule (which is 5 in your case) to avoid any uncertainty.

@fufesou
Copy link
Author

fufesou commented Aug 2, 2019

This lib stuck indicated that your chain was under a view change, which is by design. This mechanism is employed to ensure liveness against faulty leaders, temporary network partition, etc. (Please refer to the original pbft algorithm here)

The view change comes with a timeout (which in the current version is 30 secs), nodes will enter the new view subsequently. To reduce the frequency of view changes, it is suggested to 1) keep all your nodes connected with each other, 2) adjust the overload of trxns to a level that fits your machine and 3) slightly increase the size of your bp schedule (which is 5 in your case) to avoid any uncertainty.

Thank you. As you say, lib stuck wont be longer than 30 secs in my version?

  1. I have made all nodes connected to each other before.
  2. The overload is not in high level in a time.
  3. emm, hard^_^.

What if i decrease blocks that a node produce continuously。12 to 3? Will the view change timeout be shorten to 8 secs?

@fufesou
Copy link
Author

fufesou commented Aug 2, 2019 •
edited
Loading

This lib stuck indicated that your chain was under a view change, which is by design. This mechanism is employed to ensure liveness against faulty leaders, temporary network partition, etc. (Please refer to the original pbft algorithm here)

The view change comes with a timeout (which in the current version is 30 secs), nodes will enter the new view subsequently. To reduce the frequency of view changes, it is suggested to 1) keep all your nodes connected with each other, 2) adjust the overload of trxns to a level that fits your machine and 3) slightly increase the size of your bp schedule (which is 5 in your case) to avoid any uncertainty.

I've read the white paper.
"After the introduction of PBFT, in order to avoid the fork which may cause the consensus to become unable to advance, the view change mechanism is introduced. All unconsented information is discarded and consensus procedures are continually attempted until the consensus is made."

View change works until the consensus is made. You said "The view change comes with a timeout ". What if the consensus is not made after 30 secs? Is it work as the following shows?

view change --> consensus is made----(30 secs)----> view change end, lib move

Thank you

@oldcold
Copy link

oldcold commented Aug 2, 2019

View change works until the consensus is made. You said "The view change comes with a timeout ". What if the consensus is not made after 30 secs? Is it work as the following shows?

The view change will happen only if the LIB is not advancing after a period of time (say 30 secs here), and this is used to get the chain back to work.

@oldcold
Copy link

oldcold commented Aug 2, 2019

What if i decrease blocks that a node produce continuously。12 to 3? Will the view change timeout be shorten to 8 secs?

How do you achieve this? By modifying the source code?

@fufesou
Copy link
Author

fufesou commented Aug 2, 2019

What if i decrease blocks that a node produce continuously。12 to 3? Will the view change timeout be shorten to 8 secs?

How do you achieve this? By modifying the source code?

Yes

@fufesou
Copy link
Author

fufesou commented Aug 2, 2019

View change works until the consensus is made. You said "The view change comes with a timeout ". What if the consensus is not made after 30 secs? Is it work as the following shows?

The view change will happen only if the LIB is not advancing after a period of time (say 30 secs here), and this is used to get the chain back to work.

View change happens after lib stops advancing after (30 secs)? Isn't it the reason why lib is on stuck? I'm confused _

@oldcold
Copy link

oldcold commented Aug 5, 2019

View change happens after lib stops advancing after (30 secs)? Isn't it the reason why lib is on stuck? I'm confused _

LIB is likely to be frozen due to various reasons in the wild, as I have mentioned in the very first reply, and that's why the view change mechanism is needed.

In short, if LIB stop for some time, a view change action will be triggered, during the view change state, nodes will attempt to sync all pbft related information (within a reasonable range) one more time to resume the consensus.

@fufesou
Copy link
Author

fufesou commented Aug 5, 2019

View change happens after lib stops advancing after (30 secs)? Isn't it the reason why lib is on stuck? I'm confused _

LIB is likely to be frozen due to various reasons in the wild, as I have mentioned in the very first reply, and that's why the view change mechanism is needed.

In short, if LIB stop for some time, a view change action will be triggered, during the view change state, nodes will attempt to sync all pbft related information (within a reasonable range) one more time to resume the consensus.

I understand, maybe. Some statement triggers view change. View change take at least 30 secs in my version?
I'll learn pbft in a time later. Thank you for your help.

@fufesou fufesou closed this as completed Aug 8, 2019
vlbos pushed a commit to vlbos/bos that referenced this issue Sep 18, 2019
# This is a combination of 186 commits.
6c09577 
# This is the 1st commit message:

various improvements

# This is the commit message #2:

new hash

# This is the commit message #3:

fix for script path

# This is the commit message #4:

fixes

# This is the commit message #5:

fixes

# This is the commit message #6:

fixes

# This is the commit message #7:

fixes

# This is the commit message #8:

fixes

# This is the commit message #9:

fixes

# This is the commit message #10:

fixes

# This is the commit message boscore#11:

fixes

# This is the commit message boscore#12:

fixes

# This is the commit message boscore#13:

fixes

# This is the commit message boscore#14:

fixes

# This is the commit message boscore#15:

fixes

# This is the commit message boscore#16:

fixes

# This is the commit message boscore#17:

fixes

# This is the commit message boscore#18:

fixes

# This is the commit message boscore#19:

fixes

# This is the commit message boscore#20:

fixes

# This is the commit message boscore#21:

fixes

# This is the commit message boscore#22:

fixes

# This is the commit message boscore#23:

fixes

# This is the commit message boscore#24:

fixes

# This is the commit message boscore#25:

fixes

# This is the commit message boscore#26:

testing

# This is the commit message boscore#27:

testing

# This is the commit message boscore#28:

testing

# This is the commit message boscore#29:

testing

# This is the commit message boscore#30:

testing

# This is the commit message boscore#31:

testing

# This is the commit message boscore#32:

testing

# This is the commit message boscore#33:

testing

# This is the commit message boscore#34:

testing

# This is the commit message boscore#35:

testing

# This is the commit message boscore#36:

testing

# This is the commit message boscore#37:

testing

# This is the commit message boscore#38:

testing

# This is the commit message boscore#39:

testing

# This is the commit message boscore#40:

testing

# This is the commit message boscore#41:

testing

# This is the commit message boscore#42:

testing

# This is the commit message boscore#43:

testing

# This is the commit message boscore#44:

fixes

# This is the commit message boscore#45:

fixes

# This is the commit message boscore#46:

fixes

# This is the commit message boscore#47:

fixes

# This is the commit message boscore#48:

fixes

# This is the commit message boscore#49:

fixes

# This is the commit message boscore#50:

fixes

# This is the commit message boscore#51:

fixes

# This is the commit message boscore#52:

fixes

# This is the commit message boscore#53:

fixes

# This is the commit message boscore#54:

fixes

# This is the commit message boscore#55:

fixes

# This is the commit message boscore#56:

fixes

# This is the commit message boscore#57:

fixes

# This is the commit message boscore#58:

fixes

# This is the commit message boscore#59:

fixes

# This is the commit message boscore#60:

fixes

# This is the commit message boscore#61:

fixes

# This is the commit message boscore#62:

fixes

# This is the commit message boscore#63:

fixes

# This is the commit message boscore#64:

fixes

# This is the commit message boscore#65:

fixes

# This is the commit message boscore#66:

fixes

# This is the commit message boscore#67:

fixes

# This is the commit message boscore#68:

fixes

# This is the commit message boscore#69:

fixes

# This is the commit message boscore#70:

fixes

# This is the commit message boscore#71:

fixes

# This is the commit message boscore#72:

fixes

# This is the commit message boscore#73:

fixes

# This is the commit message boscore#74:

fixes

# This is the commit message boscore#75:

fixes

# This is the commit message boscore#76:

fixes

# This is the commit message boscore#77:

fixes

# This is the commit message boscore#78:

fixes

# This is the commit message boscore#79:

more testing

# This is the commit message boscore#80:

testing

# This is the commit message boscore#81:

fixes

# This is the commit message boscore#82:

fixes

# This is the commit message boscore#83:

fixes

# This is the commit message boscore#84:

fixes

# This is the commit message boscore#85:

fixes

# This is the commit message boscore#86:

fixes

# This is the commit message boscore#87:

fixes

# This is the commit message boscore#88:

fixes

# This is the commit message boscore#89:

fixes

# This is the commit message boscore#90:

fixes

# This is the commit message boscore#91:

fixes

# This is the commit message boscore#92:

fixes

# This is the commit message boscore#93:

propagate-environment for buildkite-agent

# This is the commit message boscore#94:

propagate-environment for buildkite-agent

# This is the commit message boscore#95:

propagate-environment for buildkite-agent

# This is the commit message boscore#96:

propagate-environment for buildkite-agent

# This is the commit message boscore#97:

fixes

# This is the commit message boscore#98:

fixes

# This is the commit message boscore#99:

fixes

# This is the commit message boscore#100:

fixes

# This is the commit message boscore#101:

fixes

# This is the commit message boscore#102:

fixes

# This is the commit message boscore#103:

fixes

# This is the commit message boscore#104:

fixes

# This is the commit message boscore#105:

fixes

# This is the commit message boscore#106:

fixes

# This is the commit message boscore#107:

fixes

# This is the commit message boscore#108:

fixes

# This is the commit message boscore#109:

fixes

# This is the commit message boscore#110:

fixes

# This is the commit message boscore#111:

fixes

# This is the commit message boscore#112:

fixes

# This is the commit message boscore#113:

fixes

# This is the commit message boscore#114:

fixes

# This is the commit message boscore#115:

fixes

# This is the commit message boscore#116:

fixes

# This is the commit message boscore#117:

fixes

# This is the commit message boscore#118:

fixes

# This is the commit message boscore#119:

fixes

# This is the commit message boscore#120:

fixes

# This is the commit message boscore#121:

fixes

# This is the commit message boscore#122:

fixes

# This is the commit message boscore#123:

fixes

# This is the commit message boscore#124:

fixes

# This is the commit message boscore#125:

fixes

# This is the commit message boscore#126:

fixes

# This is the commit message boscore#127:

fixes

# This is the commit message boscore#128:

fixes

# This is the commit message boscore#129:

fixes

# This is the commit message boscore#130:

fixes

# This is the commit message boscore#131:

fixes

# This is the commit message boscore#132:

fixes

# This is the commit message boscore#133:

fixes

# This is the commit message boscore#134:

fixes

# This is the commit message boscore#135:

fixes

# This is the commit message boscore#136:

fixes

# This is the commit message boscore#137:

fixes

# This is the commit message boscore#138:

fixes

# This is the commit message boscore#139:

fixes

# This is the commit message boscore#140:

fixes

# This is the commit message boscore#141:

fixes

# This is the commit message boscore#142:

fixes

# This is the commit message boscore#143:

fixes

# This is the commit message boscore#144:

fixes

# This is the commit message boscore#145:

fixes

# This is the commit message boscore#146:

fixes

# This is the commit message boscore#147:

fixes

# This is the commit message boscore#148:

fixes

# This is the commit message boscore#149:

fixes

# This is the commit message boscore#150:

fixes

# This is the commit message boscore#151:

fixes

# This is the commit message boscore#152:

fixes

# This is the commit message boscore#153:

testing

# This is the commit message boscore#154:

fixes

# This is the commit message boscore#155:

fixes

# This is the commit message boscore#156:

fixes

# This is the commit message boscore#157:

fixes

# This is the commit message boscore#158:

fixes

# This is the commit message boscore#159:

fixes

# This is the commit message boscore#160:

fixes

# This is the commit message boscore#161:

fixes

# This is the commit message boscore#162:

fixes

# This is the commit message boscore#163:

fixes

# This is the commit message boscore#164:

fixes

# This is the commit message boscore#165:

fixes

# This is the commit message boscore#166:

fixes

# This is the commit message boscore#167:

fixes

# This is the commit message boscore#168:

fixes

# This is the commit message boscore#169:

fixes

# This is the commit message boscore#170:

fixes

# This is the commit message boscore#171:

fixes

# This is the commit message boscore#172:

fixes

# This is the commit message boscore#173:

fixes

# This is the commit message boscore#174:

fixes

# This is the commit message boscore#175:

fixes

# This is the commit message boscore#176:

fixes

# This is the commit message boscore#177:

fixes

# This is the commit message boscore#178:

fixes

# This is the commit message boscore#179:

fixes

# This is the commit message EOSIO#180:

fixes

# This is the commit message EOSIO#181:

fixes

# This is the commit message EOSIO#182:

fixes

# This is the commit message EOSIO#183:

fixes

# This is the commit message EOSIO#184:

fixes

# This is the commit message EOSIO#185:

fixes

# This is the commit message EOSIO#186:

fixes
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
2 participants
@fufesou @oldcold