Scylla Delete Data Disk Space Not Release Problem

281 views
Skip to first unread message

860823346@qq.com

<860823346@qq.com>
unread,
Jul 26, 2019, 5:59:35 AM7/26/19
to ScyllaDB development
The Scylla disk is full. Recently, the deletion operation was carried out. After deletion, the disk is not released. The deletion process is due to writing rowkey to the disk. On the contrary, the disk has been increased a lot. What can I do to release the disk?

Glauber Costa

<glauber@scylladb.com>
unread,
Jul 26, 2019, 7:05:02 AM7/26/19
to 860823346@qq.com, scylladb-dev
data is really only deleted through a compaction.

Once the disk is full, though, you will not be able to run it.

The best procedure then is to add more nodes temporarily,  then execute nodetool cleanup in the old ones.

Once you are happy you can decommission the temporary nodes.



On Fri., Jul. 26, 2019, 5:59 a.m. , <8608...@qq.com> wrote:
The Scylla disk is full. Recently, the deletion operation was carried out. After deletion, the disk is not released. The deletion process is due to writing rowkey to the disk. On the contrary, the disk has been increased a lot. What can I do to release the disk?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-dev/87f79696-9915-4519-9265-20499292d02f%40googlegroups.com.

860823346@qq.com

<860823346@qq.com>
unread,
Jul 26, 2019, 10:31:43 PM7/26/19
to ScyllaDB development
Thank you very much, but I don't think this method seems very suitable for our scenario. Can we solve this problem without adding resources?

在 2019年7月26日星期五 UTC+8下午7:05:02,Glauber Costa写道:
data is really only deleted through a compaction.

Once the disk is full, though, you will not be able to run it.

The best procedure then is to add more nodes temporarily,  then execute nodetool cleanup in the old ones.

Once you are happy you can decommission the temporary nodes.



On Fri., Jul. 26, 2019, 5:59 a.m. , <8608...@qq.com> wrote:
The Scylla disk is full. Recently, the deletion operation was carried out. After deletion, the disk is not released. The deletion process is due to writing rowkey to the disk. On the contrary, the disk has been increased a lot. What can I do to release the disk?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylla...@googlegroups.com.

860823346@qq.com

<860823346@qq.com>
unread,
Jul 26, 2019, 11:47:19 PM7/26/19
to ScyllaDB development

wenti.jpeg

Above is a part of our logs after we executed the cleanup command. There is basically no printed compressed content in the logs, and the disk space does not seem to be released. We did not add new nodes, but deleted some data. In this case, does the cleanup command not work very well?


在 2019年7月26日星期五 UTC+8下午7:05:02,Glauber Costa写道:
data is really only deleted through a compaction.

Once the disk is full, though, you will not be able to run it.

The best procedure then is to add more nodes temporarily,  then execute nodetool cleanup in the old ones.

Once you are happy you can decommission the temporary nodes.


On Fri., Jul. 26, 2019, 5:59 a.m. , <8608...@qq.com> wrote:
The Scylla disk is full. Recently, the deletion operation was carried out. After deletion, the disk is not released. The deletion process is due to writing rowkey to the disk. On the contrary, the disk has been increased a lot. What can I do to release the disk?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylla...@googlegroups.com.

Glauber Costa

<glauber@scylladb.com>
unread,
Jul 29, 2019, 9:40:51 AM7/29/19
to 860823346@qq.com, ScyllaDB development
On Fri, Jul 26, 2019 at 11:47 PM <8608...@qq.com> wrote:

wenti.jpeg

Above is a part of our logs after we executed the cleanup command. There is basically no printed compressed content in the logs, and the disk space does not seem to be released. We did not add new nodes, but deleted some data. In this case, does the cleanup command not work very well?

Cleanup will not reduce your data size because it will not compact the data.
After a deletion, tombstones and data will be in different SSTables, and only a *compaction* will reduce it.
 

在 2019年7月26日星期五 UTC+8下午7:05:02,Glauber Costa写道:
data is really only deleted through a compaction.

Once the disk is full, though, you will not be able to run it.

The best procedure then is to add more nodes temporarily,  then execute nodetool cleanup in the old ones.

Once you are happy you can decommission the temporary nodes.



On Fri., Jul. 26, 2019, 5:59 a.m. , <8608...@qq.com> wrote:
The Scylla disk is full. Recently, the deletion operation was carried out. After deletion, the disk is not released. The deletion process is due to writing rowkey to the disk. On the contrary, the disk has been increased a lot. What can I do to release the disk?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylla...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-dev/87f79696-9915-4519-9265-20499292d02f%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "ScyllaDB development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-dev/56f540f2-6c2c-4288-b732-1e80d3b06606%40googlegroups.com.

860823346@qq.com

<860823346@qq.com>
unread,
Jul 30, 2019, 3:46:57 AM7/30/19
to ScyllaDB development
Well, thank you very much.

在 2019年7月29日星期一 UTC+8下午9:40:51,Glauber Costa写道:


Glauber Costa

<glauber@scylladb.com>
unread,
Jul 30, 2019, 8:17:46 AM7/30/19
to 860823346@qq.com, ScyllaDB development
You are welcome!

Let us know how it goes.


To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-dev/ba126a22-88e9-479b-a40a-cc3e0c25a3fd%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages