BitShares Forum
Main => General Discussion => Topic started by: alt on July 20, 2014, 11:41:50 pm
-
delgate-alt always missed block, the reliability is only 59.49%.
I have see the debug message, every time when I missed block, the rebraodcast_pending was called with a high latency.
not missed, block 15080
20140720T231440.007245 th_a apply_transactions ] Applying transactions from block: 15080 chain_database.cpp:962
20140720T231440.007312 th_a execute_markets ] execute markets [] chain_database.cpp:1182
20140720T231441.788079 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
20140720T231441.788197 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
missed, block 14971
20140720T225620.008000 th_a apply_transactions ] Applying transactions from block: 14971 chain_database.cpp:962
20140720T225620.008105 th_a execute_markets ] execute markets [] chain_database.cpp:1182
20140720T225629.770625 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
20140720T225629.770730 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
not missed, block 14888
20140720T224220.008251 th_a apply_transactions ] Applying transactions from block: 14888 chain_database.cpp:962
20140720T224220.008319 th_a execute_markets ] execute markets [] chain_database.cpp:1182
20140720T224224.754508 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
20140720T224224.754577 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
missed, block 14649
20140720T220210.011105 th_a apply_transactions ] Applying transactions from block: 14649 chain_database.cpp:962
20140720T220210.012315 th_a execute_markets ] execute markets [] chain_database.cpp:1182
20140720T220210.012778 th_a store_balance_record ] balance record: {"balance":16394400,"condition":{"asset_id":0,"delegate_slate_id":5360468550988535606,"type": "withdraw_signature_type","data":{"owner":"BTSXDAKNtbVobxaYtLTu4QqdKLsgh2dQA2F5P","memo":{"one_time_key":"B 20140720T220210.011105 th_a apply_transactions ] Applying transactions from block: 14649 chain_database.cpp:962
TSX5pP2PcD7or578RUGu752Dgrh3TPnfawpFV2TBcQo5wFWmG9TGD","enc rypted_memo_data":"53b5be02a0adc07bf331e2a7f5b2a7ad53aa16d88ba6b00be555b1a42b369131db17d2c3cff05118e212047f79cff39f25b60ba274e2aa535ded27d9542e1a2b"}}},"genesis_info" :null,"last_update":"20140720T220 20140720T220210.012315 th_a execute_markets ] execute markets [] chain_database.cpp:1182
200"} chain_database.cpp:1816
20140720T220219.703103 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
20140720T220219.703280 th_a rebroadcast_pending ] rebroadcasting... client.cpp:857
-
I haven't got a clue, but I find it interesting that the latency in both cases shown was about 9.7 seconds. Is that the case for all of the missed blocks?
Now that I look the latency on the non missed blocks was 1.7 and 4.7. Probably totally unrelated, but an interesting coincidence.
-
the latency is very weired
some is very high, some is negative
this never happened at the dry run
15367 2014-07-21T00:03:10 bitsharesxfc 1 357 0.10015 BTSX 5 0.004493
15366 2014-07-21T00:03:00 init63 1 357 0.10015 BTSX 6 0.003735
15365 2014-07-21T00:02:50 init85 2 552 0.20030 BTSX 16 0.005051
15364 2014-07-21T00:02:40 clout-delegate1 1 357 0.10015 BTSX 26 0.004266
15363 2014-07-21T00:02:30 init52 0 166 0.00000 BTSX 0 0.003344
15362 2014-07-21T00:02:20 init22 1 357 0.10015 BTSX 0 0.004134
15361 2014-07-21T00:02:10 init8 0 166 0.00000 BTSX 0 0.002837
15360 2014-07-21T00:02:00 needle 2 548 0.20030 BTSX 5 0.005291
15359 2014-07-21T00:01:50 init12 0 166 0.00000 BTSX 2 0.003132
15358 2014-07-21T00:01:40 init67 0 166 0.00000 BTSX 0 0.002877
15357 2014-07-21T00:01:30 delegated-proof-of-steak 0 166 0.00000 BTSX 0 0.002963
15356 2014-07-21T00:01:20 bts500rmb 1 357 0.10015 BTSX 0 0.005569
15355 2014-07-21T00:01:10 init81 2 549 0.20030 BTSX 0 0.005814
15354 2014-07-21T00:01:00 init48 2 548 0.20030 BTSX 0 0.005575
15353 2014-07-21T00:00:50 jabbajabba 1 357 0.10015 BTSX -5 0.004535
MISSED 2014-07-21T00:00:40 primecoin N/A N/A N/A N/A N/A
15352 2014-07-21T00:00:30 clout-delegate3 1 357 0.10015 BTSX 1 0.008502
15351 2014-07-21T00:00:20 init4 1 357 0.10015 BTSX 0 0.004744
15350 2014-07-21T00:00:10 init55 0 166 0.00000 BTSX 5 0.003213
15349 2014-07-21T00:00:00 oathkeeper 0 166 0.00000 BTSX 5 0.002751
-
this from another machine.
15367 2014-07-21T00:03:10 bitsharesxfc 1 357 0.10015 BTSX 5 0.008251
15366 2014-07-21T00:03:00 init63 1 357 0.10015 BTSX -1 0.005289
15365 2014-07-21T00:02:50 init85 2 552 0.20030 BTSX -1 0.022577
15364 2014-07-21T00:02:40 clout-delegate1 1 357 0.10015 BTSX -1 0.009967
15363 2014-07-21T00:02:30 init52 0 166 0.00000 BTSX -1 0.007651
15362 2014-07-21T00:02:20 init22 1 357 0.10015 BTSX -1 0.005246
15361 2014-07-21T00:02:10 init8 0 166 0.00000 BTSX -1 0.044978
15360 2014-07-21T00:02:00 needle 2 548 0.20030 BTSX 4 0.006669
15359 2014-07-21T00:01:50 init12 0 166 0.00000 BTSX 0 0.006591
15358 2014-07-21T00:01:40 init67 0 166 0.00000 BTSX -1 0.008082
15357 2014-07-21T00:01:30 delegated-proof-of-steak 0 166 0.00000 BTSX -1 0.008805
15356 2014-07-21T00:01:20 bts500rmb 1 357 0.10015 BTSX -1 0.009422
15355 2014-07-21T00:01:10 init81 2 549 0.20030 BTSX -1 0.005314
15354 2014-07-21T00:01:00 init48 2 548 0.20030 BTSX -1 0.004157
15353 2014-07-21T00:00:50 jabbajabba 1 357 0.10015 BTSX -9 0.009978
MISSED 2014-07-21T00:00:40 primecoin N/A N/A N/A N/A N/A
-
the latency is very weired
some is very high, some is negative
this never happened at the dry run
15367 2014-07-21T00:03:10 bitsharesxfc 1 357 0.10015 BTSX 5 0.004493
15366 2014-07-21T00:03:00 init63 1 357 0.10015 BTSX 6 0.003735
15365 2014-07-21T00:02:50 init85 2 552 0.20030 BTSX 16 0.005051
15364 2014-07-21T00:02:40 clout-delegate1 1 357 0.10015 BTSX 26 0.004266
15363 2014-07-21T00:02:30 init52 0 166 0.00000 BTSX 0 0.003344
15362 2014-07-21T00:02:20 init22 1 357 0.10015 BTSX 0 0.004134
15361 2014-07-21T00:02:10 init8 0 166 0.00000 BTSX 0 0.002837
15360 2014-07-21T00:02:00 needle 2 548 0.20030 BTSX 5 0.005291
15359 2014-07-21T00:01:50 init12 0 166 0.00000 BTSX 2 0.003132
15358 2014-07-21T00:01:40 init67 0 166 0.00000 BTSX 0 0.002877
15357 2014-07-21T00:01:30 delegated-proof-of-steak 0 166 0.00000 BTSX 0 0.002963
15356 2014-07-21T00:01:20 bts500rmb 1 357 0.10015 BTSX 0 0.005569
15355 2014-07-21T00:01:10 init81 2 549 0.20030 BTSX 0 0.005814
15354 2014-07-21T00:01:00 init48 2 548 0.20030 BTSX 0 0.005575
15353 2014-07-21T00:00:50 jabbajabba 1 357 0.10015 BTSX -5 0.004535
MISSED 2014-07-21T00:00:40 primecoin N/A N/A N/A N/A N/A
15352 2014-07-21T00:00:30 clout-delegate3 1 357 0.10015 BTSX 1 0.008502
15351 2014-07-21T00:00:20 init4 1 357 0.10015 BTSX 0 0.004744
15350 2014-07-21T00:00:10 init55 0 166 0.00000 BTSX 5 0.003213
15349 2014-07-21T00:00:00 oathkeeper 0 166 0.00000 BTSX 5 0.002751
Maybe you should make your delegate node more close to the seed node any other delegate node, especially for those with high latency to you, but they have higher reliability.