From a487ef1ff369cb2ec86e7fc32f33f111c7f27509 Mon Sep 17 00:00:00 2001
From: "Raphael S. Carvalho" <raphaelsc@scylladb.com>
Date: Thu, 11 Feb 2016 20:46:35 -0200
Subject: [PATCH] sstables: improve log message when a sstable is sealed

Signed-off-by: Raphael S. Carvalho <raphaelsc@scylladb.com>
Message-Id: <e391243212d83347b1b50c728bee24f6a2ecc950.1455230788.git.raphaelsc@scylladb.com>
---
 sstables/sstables.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sstables/sstables.cc b/sstables/sstables.cc
index fbc9c5c2c0..c9dc7053a2 100644
--- a/sstables/sstables.cc
+++ b/sstables/sstables.cc
@@ -785,7 +785,7 @@ void sstable::seal_sstable() {
     dir_f.flush().get();
     dir_f.close().get();
     // If this point was reached, sstable should be safe in disk.
-    sstlog.debug("SSTable with generation {} was sealed successfully.", _generation);
+    sstlog.debug("SSTable with generation {} of {}/{} was sealed successfully.", _generation, _ks, _cf);
 }
 
 void write_crc(const sstring file_path, checksum& c) {