-
Task
-
Resolution: Won't Do
-
Medium
-
None
-
None
The disk usage of onap-nfs-server increases 2GB per day even though the ONAP environment is idle.
Upon investigation we found　elasticsearch log is consuming more space.
How can we manage the file usage?
Is normal operation in ONAP that the disk usage of onap-nfs-server keeps increasing?
What happens when the disk space is full in onap-nfs-server?
How is log rotation done in elasticsearch?
Details of file usage are as follows. (Extracted folders over 1GB)
-At first confirmation
ubuntu@onap-nfs-server:~$ sudo du -h / | sort -rh | head -50 22G /dockerdata-nfs 4.7G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices 1.9G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/V3FxiYuFTMqF9qaq8r29Rw 1.6G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/1mhZopAYROm1Gma-EtFvZA 1.3G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/7As-daTZSrWqVOImc7Q4fg
-Two days later
ubuntu@onap-nfs-server:~$ sudo du -h / | sort -rh | head -50 35G /dockerdata-nfs 8.8G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices 2.8G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/IJj-4wd0Sou3Coa_FjlrRg 1.6G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/wel4rXT2QCOpQ2KjGo_dzA 1.6G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/V3FxiYuFTMqF9qaq8r29Rw 1.6G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/1mhZopAYROm1Gma-EtFvZA 1.3G /dockerdata-nfs/dev-log/log/elasticsearch/data/nodes/0/indices/7As-daTZSrWqVOImc7Q4fg
