Hi Linquer,

I am  trying to run with the configuration that you suggested on 500 GB
data , can you please verify the below properties.

*config.queries*
coordinator=true
node-scheduler.include-coordinator=true
http-server.http.port=8086
query.max-memory=5GB
#query.max-memory-per-node=1GB
discovery-server.enabled=true
discovery.uri=http://xx.xx.xx.xx:8086
<http://www.google.com/url?q=http%3A%2F%2F46.4.88.233%3A8086&sa=D&sntz=1&usg=AFQjCNEjpC9wVuY-DNEiGBrOUyQOy3cMjg>
*jvm.config*
-server
-Xmx16G
-XX:+UseG1GC
-XX:G1HeapRegionSize=32M
-XX:+UseGCOverheadLimit
-XX:+ExplicitGCInvokesConcurrent
-XX:+HeapDumpOnOutOfMemoryError
-XX:OnOutOfMemoryError=kill -9 %p
-XX:ReservedCodeCacheSize=1G

Regards
Bhavya

On Mon, Jul 3, 2017 at 11:45 AM, Bhavya Aggarwal <[EMAIL PROTECTED]> wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB