BitShares Forum

Main => 中文 (Chinese) => Topic started by: alt on July 30, 2014, 09:30:10 am

Title: 100%出块,连续4个小时没丢块了
Post by: alt on July 30, 2014, 09:30:10 am
从 block 91576 到现在(93040) 连续4个多小时没丢一个块了
可喜可贺
Title: Re: 100%出块,连续4个小时没丢块了
Post by: woolcii on July 30, 2014, 09:46:13 am
9万多块了啊 厉害啊
Title: Re: 100%出块,连续4个小时没丢块了
Post by: Snail on July 30, 2014, 09:49:05 am
 +5% +5%
Title: Re: 100%出块,连续4个小时没丢块了
Post by: Webber on July 30, 2014, 10:07:17 am
受托人都越来越专业了 :P :P :P
Title: Re: 100%出块,连续4个小时没丢块了
Post by: COMMSSL on July 30, 2014, 10:35:08 am
支持ALT
Title: Re: 100%出块,连续4个小时没丢块了
Post by: bitshare007777 on July 30, 2014, 10:56:10 am
初始受托人数量降到个位数就完美了 +5%
Title: Re: 100%出块,连续4个小时没丢块了
Post by: willaim on July 30, 2014, 07:38:53 pm
<悟空是个好员工>,这本书还有人记得吗? alt就是一个杰出的员工, 我建议alt公开你的别名.我们给你捐献表示敬意!曾经和您共同战斗,是我的荣幸!
Title: Re: 100%出块,连续4个小时没丢块了
Post by: sfinder on July 30, 2014, 07:51:38 pm
alt老弟,这个slave客户端只要加“ next_slot_time += 5;”这行代码后编译,是吗?

slave可以和master同时开机而不会相互影响吗?一个代表运行在2个不同的结点是否是BM所允许的。

你做过多少测试?


hi, delegates. we have a solution for hot standby.

set up delegate wallet in 2 machines. one is master, and the other is slave.
master run  delegate_loop task at seconds 0,10,20 ....
slave run the task with 5 seconds delay, at 5, 15, 25 .....
Normally master will generate block in time, slave will receive the block less than 5 seconds, than slave will not generate block.
If for some reason, master missed generation, slave didn't receive block from master in 5 seconds, slave will generate.

here is the patch for slave program:
Code: [Select]
--- a/libraries/client/client.cpp
+++ b/libraries/client/client.cpp
@@ -729,6 +729,7 @@ config load_config( const fc::path& datadir )
 
           uint32_t slot_number = blockchain::get_slot_number( now );
           time_point_sec next_slot_time = blockchain::get_slot_start_time( slot_number + 1 );
+          next_slot_time += 5;
           ilog( "Rescheduling delegate loop for time: ${t}", ("t",next_slot_time) );
 
           time_point scheduled_time = next_slot_time;
Title: Re: 100%出块,连续4个小时没丢块了
Post by: sfinder on July 30, 2014, 10:20:28 pm


ALT会出下面这个问题吗
This will likely cause you to sign 2 different blocks.
How you ensure that they will not sign 2 different blocks ?
Title: Re: 100%出块,连续4个小时没丢块了
Post by: yinchanggong on July 30, 2014, 10:38:16 pm
alt大神不解释
Title: Re: 100%出块,连续4个小时没丢块了
Post by: alt on July 30, 2014, 11:52:43 pm
<悟空是个好员工>,这本书还有人记得吗? alt就是一个杰出的员工, 我建议alt公开你的别名.我们给你捐献表示敬意!曾经和您共同战斗,是我的荣幸!
哈,谢谢支持,我的帐号在签名上有  :D
Title: Re: 100%出块,连续4个小时没丢块了
Post by: alt on July 30, 2014, 11:56:17 pm


ALT会出下面这个问题吗
This will likely cause you to sign 2 different blocks.
How you ensure that they will not sign 2 different blocks ?
有可能的,如果 master 生产了块,但 slave 没在5s内收到,就会生成第2个块了。
所以要运行 network_add_node 让 slave 和 master 直连降低它们的通讯 latency.
正常情况是不会有这么大延迟
据说以后会禁止签两个块,到时我们会根据新的规则更新方案,能保证不违规  :)
Title: Re: 100%出块,连续4个小时没丢块了
Post by: sfinder on July 31, 2014, 02:25:15 am
完全不丢块很难,我换了2个服务器了,其中有个服务器用的是ssd还是丢块。连接数好像和主机提供商有关系,用www.hp.com/helion‎和azure.microsoft.com的云服务器运行5天了链接数都保持20以上。一般的VPS连接数没20小时都要重设
Title: Re: 100%出块,连续4个小时没丢块了
Post by: Overthetop on July 31, 2014, 04:55:26 am
 +5%
Title: Re: 100%出块,连续4个小时没丢块了
Post by: king on July 31, 2014, 05:23:56 am
我的mister的块,基本是初期安装时丢的,正式运营之前,
已经丢了达77个块,之后两次更换钱包版本,又丢了6个块.
在正常运行状态下丢的,只有一块!!!!