-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insufficient memory issue #4
Comments
Hey Sidi, This probably means the JRE is configured to run with 8g memory but there On Thursday, June 16, 2016, Sidi Chang [email protected] wrote:
|
Hi Bengecko, I am using Amazon AWS m4.large which should give me 8G or 16GB memory. I have one master and three workers. All the four machines are Kafka broker, the master node is the Spark Streaming seed node and Cassandra node. I run the data generator and put the throughput into the second worker, but it will give me this bug. Do you have any idea on this? |
If you AWS instance is configured with 8g then you will want to up it to Run: free -m To see how much memory you have. Also run: ps -ef | grep java Then copy and paste output into this thread. On Friday, June 17, 2016, Sidi Chang [email protected] wrote:
|
Hi, After running the second command, the output is |
OK so it definitely looks like there is not enough memory on the machine to run the java process in question. There is always a certain amount of memory used for the operating system so if the java process is asking for more memory than is available, you’ll see the error you mentioned. My conclusion is you need more RAM on the AWS instance. 16G should be fine. Basically the java process needs room to allocate more memory as needed.
|
Hi, Thank you! I re-ordered the AWS node and spent some time to trouble shooting with my Finally everything is finished and works fine. I really thank you for your Best, Sidi
Sidi CHANG |
Sidi, My pleasure I'm glad we got through it :) On Friday, June 17, 2016, Sidi Chang [email protected] wrote:
|
I try to throw my data directly into Kafka but it seems like there are some bugs with that.
Now: 2015-07-12T14:02:31.332, Events:60000, Rate: 4401 epsJava HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x00000006c9000000, 830472192, 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 830472192 bytes for committing reserved memory.
An error report file with more information is saved as:
/home/ubuntu/eventsim/hs_err_pid3267.log
ubuntu@ip-172-31-1-10:~/eventsim$ rm hs_err_pid3267.log
The text was updated successfully, but these errors were encountered: