This is an issue with Postgres specifically and is therefore not related to the JVM. Most likely it is failing to temporarily store data during a big query due to low capacity.
If you have plentiful physical capacity on the disk you could have a look at https://www.postgresql.org/docs/9.5/static/runtime-config-resource.html Specifically see section 18.4.2 which addresses the temp_file_limit. Also try to do a VACUUM FULL On Fri, Jun 17, 2016 at 3:26 PM, Raminosoa Rabemanantsoa, Tantely < [email protected]> wrote: > Hi All, > > Thank you for your points of view. I am just wondering on this disk > capacity issue. We are using a cloud Amazon Web services to host the DHIS2 > application. There are 80 gigabyte disk space used only by DHIS2. There are > 30 gigabyte of RAM where 9 GB are for JVM and 9 GB for postgreSQL. My > question is that which parameters should I correct to troubleshoot this > disk issue as physically there is still large available disk space on the > server, or is there other parameters to allocate the physical disk space > (in addition to the RAM) managed by JVM? > > Thank you. > > Tantely. > > *This message and its attachments are confidential and solely for the > intended recipients. If received in error, please delete them and notify > the sender via reply e-mail immediately.* > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-users > Post to : [email protected] > Unsubscribe : https://launchpad.net/~dhis2-users > More help : https://help.launchpad.net/ListHelp > > -- Halvdan Hoem Grelland Software developer, DHIS 2 University of Oslo http://www.dhis2.org <https://www.dhis2.org/>
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
