crimson/os/seastore/cache: avoid double increments

reseting a txn doesnt really create a new one semantically.
avoid incrementing "created" on reset, otherwise we end up
with inflated numbers where MUTATE txn created count
is twice as higher than committed.

Note, "resets" are already tracked as invalidated.

Signed-off-by: Matan Breizman <mbreizma@redhat.com>

diff --git a/src/crimson/os/seastore/cache.h b/src/crimson/os/seastore/cache.h
index e6ebb2a72670a04416d4cfb6185ac62e61519b92..ce1d38607ebbbab8b22fa869a9e1440676a4eaa8 100644 (file)
--- a/src/crimson/os/seastore/cache.h
+++ b/src/crimson/os/seastore/cache.h
@@ -141,7 +141,6 @@ public:
     LOG_PREFIX(Cache::reset_transaction_preserve_handle);
     if (t.did_reset()) {
       SUBDEBUGT(seastore_t, "reset", t);
-      ++(get_by_src(stats.trans_created_by_src, t.get_src()));
     }
     t.reset_preserve_handle();
   }