Triple failure rate 15%: AssertionFailed("confirmation from Participant(x) did not match expectation")
#923
Labels
AssertionFailed("confirmation from Participant(x) did not match expectation")
#923
Most of
faled to generate some triples
in the logs, the reason is nottriple protocol time out
, but[AssertionFailed("confirmation from Participant(x) did not match expectation")]
Take dev 6 node as an example. From 8.31 am to 9.31 am Nov 6 PST time(gcp log link), there are 156 times of
faled to generate some triples
, but only 13 among those are timeouts. So (156-13)/156 = 91.7% of all failed triple generators failed because ofAssertionFailed("confirmation from Participant(x) did not match expectation")
.We need to figure out why this error would happen.
The text was updated successfully, but these errors were encountered: