Deleting data

[Boris Keleman]

Hi everyone 

We have warp10 database size of 19,2GB and the Java is using 18GB of RAM. The warp was becoming unresponsive, basic FETCH function executes 160 seconds for no data points.

So we try to delete all data but the size of the database is even growing and the 

Java is still using 18GB of RAM even after deleting all data.

The parameter we used for deleting :api/v0/delete?selector=~.*{}&deleteall

Any recommendation on how to approach deleting data?

Thank you for answers.

[Pierre]

Hello,

I don't know your use case, and it might be confidential. Several problems here:

- If you need 19GB of RAM, you must have ++10 millions of timeseries, or series with huge labels/attributes. There might be a data modelisation problem, we can help you (support contract + NDA needed). 

- Deleting data won't release RAM immediately (java will keep allocated RAM, up to the WARP10_HEAP limit you defined in your Warp 10 startup script.

- Deleting data won't release disk immediately (you need to wait for leveldb compaction cycles)

- api/v0/delete?selector=~.*{}&deleteall  => should be OK, try to url encode the {} : api/v0/delete?deleteall&selector=~.*%7B%7D

Note : On a standalone version, if your purpose is just to restart from scratch, you can just stop warp10, delete all the /leveldb/*  files, restart warp10. It won't affect tokens nor change anything.

[Mathias Herberts]

Also know that SenX is offering a commercial Warp 10 extension to support immediate release of disk space upon deletion.

Please send enquiry to sa...@senx.com for further information.

[Boris Keleman]

Hi, 

Thank you both for the reply, we deleted all leveldb files and that release space on the disk and the memory.  

regards.

[Boris Keleman]

Hi, 

After deleting leveldb files, warp is not working. we continuously get this warning; script.WarpFleetMacroRepository - No validator macro, default macro will reject all URLs. Any idea what could be wrong?

thank you.

regards.

[Mathias Herberts]

Hi Boris,

this warning is perfectly normal. It is related to the WarpFleet Resolver which can have a macro set in 'warpfleet.macros.validator' to validate URLs passed to the functions SETREPO and ADDREPO.

You can safely ignore this warning.