You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are missing important information that are required to troubleshoot concurrency-related issues. For instance in devnet220 in layer 8345 there are 2 proposals that are created with old base ballots and without votes for recent layers. It indicates that the hare didn't complete on those smeshers, while the rest of the cluster completed hare successfully.
With loki there is simpler version of the client . it needs to be integrated as a WriteSyncer to zap.Core . The client itself batches log entries in the background and instrumented with relevant metrics, so that we will know if logger will use a lot of traffic.
## Motivation
<!-- Please mention the issue fixed by this PR or detailed motivation -->
part of #3134
<!-- `Closes #XXXX, closes #XXXX, ...` links mentioned issues to this PR and automatically closes them when this it's merged -->
## Changes
<!-- Please describe in detail the changes made -->
using systests TestAddNodes as measurement of the log file for a node.
- before 4.3M
- with hare reduced 1.6M (1st commit) (-62.79%)
- with the rest of the change 1.2M (-9.3%)
We are missing important information that are required to troubleshoot concurrency-related issues. For instance in devnet220 in layer 8345 there are 2 proposals that are created with old base ballots and without votes for recent layers. It indicates that the hare didn't complete on those smeshers, while the rest of the cluster completed hare successfully.
There are two options:
I prefer to go with 1st option
The text was updated successfully, but these errors were encountered: