Hello Everyone, I am getting below error on Datahub:- An unknown error occurred. (code 500) gms logs are as below and we are using quickstart:- Suppressed: org.opensearch.client.ResponseException: method [POST], host [http://elasticsearch:9200], URI [/datahubpolicyindex_v2/_search?typed_keys=true&max_concurrent_shard_requests=5&search_type=query_then_fetch&batched_reduce_size=512&ccs_minimize_roundtrips=false], status line [HTTP/1.1 404 Not Found] {"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [datahubpolicyindex_v2]","resource.type":"index_or_alias","resource.id":"datahubpolicyindex_v2","index_uuid":"_na_","index":"datahubpolicyindex_v2"}],"type":"index_not_found_exception","reason":"no such index [datahubpolicyindex_v2]","resource.type":"index_or_alias","resource.id":"datahubpolicyindex_v2","index_uuid":"_na_","index":"datahubpolicyindex_v2"},"status":404} at org.opensearch.client.RestClient.convertResponse(RestClient.java:375) at org.opensearch.client.RestClient.performRequest(RestClient.java:345) at org.opensearch.client.RestClient.performRequest(RestClient.java:320) at org.opensearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1918) Any leads or information on this would be appreciated. Thanks!

@brainy-tent-14503 might be able to speak to this!

Hello @brainy-tent-14503, For the above issue we have tried to increase the memory of the instance from 30Gib to 40 Gib, but again the same error is coming as above. Below is the stats after memory increase. Filesystem Size Used Avail Use% Mounted on /dev/root 39G 26G 13G 67% / tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs 1.6G 1.7M 1.6G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock /dev/nvme0n1p15 98M 6.3M 92M 7% /boot/efi tmpfs 782M 4.0K 782M 1% /run/user/1000 CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 9165df48ed02 elasticsearch 0.11% 865.4MiB / 1GiB 84.51% 345MB / 252MB 109MB / 2.34GB 91 Kindly suggest on the above issue. Thanks.

Hi, are you was resolve this issue? @able-ghost-38838

Hi @microscopic-wolf-34410, I have just removed all the dangling images which had no running containers associated with them and then it worked as most of the occupied space got freed up.

After that you never have same issues again? @able-ghost-38838

@microscopic-wolf-34410 , till now I haven’t faced this issue after freeing up space as it was showing 80% above space as occupied

Will do it, thank you for your insight @able-ghost-38838