When we try to start a newly setup/existing ComputeDB cluster it fails with the below error. 

====

./snappy-start-all.sh 
Logs generated in /opt/TIB_compute_1.2.0_linux/work/localhost-locator-1/snappylocator.log
SnappyData Locator pid: 13789 status: running
  Distributed system now has 1 members.
  Started Thrift locator (Compact Protocol) on: localhost/127.0.0.1[1527]
Logs generated in /opt/TIB_compute_1.2.0_linux/work/localhost-server-1/snappyserver.log
SnappyData Server pid: 14115 status: running
  Distributed system now has 2 members.
  Started Thrift server (Compact Protocol) on: localhost/127.0.0.1[1528]
Exception in thread "main" java.io.IOException: No available status. Either status file ".snappyleader.stat" is not readable or reading the status file timed out.
	at com.gemstone.gemfire.internal.shared.LauncherBase.waitForRunning(LauncherBase.java:460)
	at io.snappydata.tools.QuickLauncher.start(QuickLauncher.java:256)
	at io.snappydata.tools.QuickLauncher.main(QuickLauncher.java:74)
=========

NOTE: This issue can occur on Server node and Locator node too

Please refer to the log files for the leadnode i.e "start_snappyleader.log". If the occurrence of issue is for server node or locator node, you can refer to "start_snappyserver.log" and "start_snappylocator.log" log files respectively. Below is the error message from "start_snappyleader.log"

==============
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007fb948000000, 67847061504, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 67847061504 bytes for committing reserved memory.
# An error report file with more information is saved as:
# <SNAPPY_DIR>/work/localhost-lead-1/hs_err_pid14329.log
===============
 

When we try to start a newly setup/existing ComputeDB cluster it fails with the below error. "No available status. Either status file ".snappyleader.stat" is not readable or reading the status file timed out."

All Supported Operating Systems

As per the "start_snappyleader.log" log file, the host does not have enough RAM to allocate the requested memory to that process (lead, in this case). In such a case, you can re-configure the memory required for that process in its configuration file under conf/ directory. For the lead process, the file is conf/leads. For servers and locators, the files are conf/servers and conf/locators, respectively.