kevinrr888 commented on issue #4498:
URL: https://github.com/apache/accumulo/issues/4498#issuecomment-2101341880
> `It just seems like a bug that it is continually reported as being in
progress on a certain step when it has already completed.`
>
> Are you questioning the reporting or the value? If it is a counter, then
systems like Prometheus will end up calculating the delta between measurements.
If it should be a gauge, then yes, it should be reset
We can see in the first set of logs that there is one transaction in
progress:
```
2024-05-08T10:32:56,013 [accumulo.METRICS] INFO :
accumulo.fate.tx{host=groot,instance.name=miniInstance,port=34595,process.name=manager,state=in_progress}
value=1
```
It also shows the operation that transaction is currently on in that same
set of logs:
```
2024-05-08T10:32:56,013 [accumulo.METRICS] INFO :
accumulo.fate.ops.in.progress.by.type{host=groot,instance.name=miniInstance,op.type=TABLE_COMPACT,port=34595,process.name=manager}
value=1
```
This is all fine/expected
One second later, when the next set of logs occur, there are zero
transactions in progress:
```
2024-05-08T10:32:57,014 [accumulo.METRICS] INFO :
accumulo.fate.tx{host=groot,instance.name=miniInstance,port=34595,process.name=manager,state=in_progress}
value=0
```
But we still see the same log that there is a transaction on operation
TABLE_COMPACT:
```
2024-05-08T10:32:57,014 [accumulo.METRICS] INFO :
accumulo.fate.ops.in.progress.by.type{host=groot,instance.name=miniInstance,op.type=TABLE_COMPACT,port=34595,process.name=manager}
value=1
```
The compaction has completed, so it seems wrong that this is still logged
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
