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.

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

[Mt-batcher]: mt-batcher pushes one less block #1366

Open
HXHke opened this issue Sep 25, 2023 · 0 comments
Open

[Mt-batcher]: mt-batcher pushes one less block #1366

HXHke opened this issue Sep 25, 2023 · 0 comments

Comments

@HXHke
Copy link
Contributor

HXHke commented Sep 25, 2023

Describe the bug

  1. When mt-batch pushes the batch to da, da will process less of the last block, resulting in one less block of data in this batch. The data of this block will not be integrated into da until the next batch.
  2. If there is no batch, the currentL2TransactionIndex metric will decrease, which is theoretically not possible. It is a counter type Prometheus monitoring.

Screenshots

  1. Mt-batcher n/a
  2. image

How to deal

  1. Mt-batcher adds a block when processing each batch.
  2. This metric is only pushed when the batch exists.
HXHke added a commit that referenced this issue Sep 26, 2023
# Goals of PR

Core changes:

1. mt-batcher adds a block when pushing each batch
2. This metric is only pushed when the batch exists.

Notes:

- no

Related Issues:

- #1366
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant