-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
'docker-compose up' cannot startup #201
Comments
@ascrutae Es image didn't start up? |
es-server_1 | [2017-05-25T07:04:36,982][INFO ][o.e.n.Node ] [TestNode] initializing ... |
This issue caused by that Elasticsearch uses a hybrid mmapfs / niofs directory by default to store its indices. The default operating system limits on mmap counts is likely to be too low. You may execute the following command on docker host. sysctl -w vm.max_map_count=262144 |
This issue caused by the collector server configuration of webui not changed. I rebuild the image. :-) |
it works! thx |
@snecker Thanks for your feedback. Closing this issue. |
same error with 3.1-2017. |
Can you post you error message? |
|
you may be add the following configuration under the
The configuration file should be like this after you add the configuration
|
feel embarrassed. After setting ES_JAVA_OPTS=-Xms150m -Xmx150m, skywalking31_es-server_1 exited with code 137. |
@aliluyahoho The memory requirement isn't up to us. We use the ElasticSearch as persistence service, and this section of docker-compose is for starting it. So it is up to ElasticSearch. 220M seems too less.... and if you only have 220M, how can you be sure the elasticsearch won't slow everything down? |
If you just want to run test or demonstration, the only option I known is waiting for v3.2. In the next version, the PM ( @pengys5 ) intends to provide a standalone mode, which only use H2-in-memory-mode to run our collector, instead of ElasticSearch for easier usage and less memory requirement. But if you requirement is running in Product env, either docker-compose or standalone mode are NOT a good choice. I highly recommend to use ElasticSearch Cluster. Hope these help. Let me know, if you have any more question. BTW, can you help to Start and Fork our project for supporting us? Thanks anyway. |
@wu-sheng Thx for your question. I will get my cloud machine configuration upgrade , then try again . This time is my personal trial. If it makes our team's requirement, we maybe running in product env. thx a lot. |
@aliluyahoho Wait for any feedback. Hope 3.2 will help more people, since we added new features about JVM and service, and improved performance. Closing this. Open this or new, if you have something to discuss. |
console print that
The text was updated successfully, but these errors were encountered: