5 ms·

"Users who tested the beta and release candidate versions of v1.0 reported huge improvements in performance and stability. Some of them were unable to crash the

by koliber 12y ago

"Users who tested the beta and release candidate versions of v1.0 reported huge improvements in performance and stability. Some of them were unable to crash the system no matter how hard they tried." This statement from the page makes me conclude that others were indeed able to crash the system, perhaps without even trying too hard. My guess is that the statement should be re-worded.

lennartkoopmann 12y ago
That is a very good point. We are in the process of changing that. :) The meaning should be that with v1.0 it is finally very hard to crash the system by overloading it. Previous versions were easier to crash by filling memory in load spike situations for example.
tbdr 12y ago
I was able to crash the system without even trying. After waiting for a 500MB something docker image download and running the container halted the host OSX machine while looping with errors (failed API connections, failed to load SIGAR, ...) The screenshots looked great but the first steps experience were a deal breaker.
- real_joschi 12y ago
  We've tested the Docker image on Mac OS X with boot2docker but of course there are always things that can go wrong. It would be awesome if you could help us improve the Docker image by creating an issue at https://github.com/Graylog2/graylog2-images/issues https://github.com/Graylog2/graylog2-images/issues with the error messages you've encountered when starting the container.
- nonane 12y ago
  I just tried this with boot2docker on a OS X machine (Yosemite) and it went very smoothly.
- deleted 12y ago
  [deleted]
- teacup50 12y ago
  Maybe requiring a full VM when a standalone self-contained application will do is not the winning strategy.
  - real_joschi 12y ago
    Oh, we got both kinds. We got country and western. ;-) Seriously, the Docker image and the VM images are there to help people getting started and to quickly try out Graylog. We also offer regular OS packages in DEB and RPM formats (supporting Debian 7, Ubuntu 12.04 and 14.04, and CentOS 6) and a quick setup application (for a simple demo setup of Graylog and its dependencies). So choose your poison and be happy!

by koliber 12y ago

lennartkoopmann 12y ago

That is a very good point. We are in the process of changing that. :) The meaning should be that with v1.0 it is finally very hard to crash the system by overloading it. Previous versions were easier to crash by filling memory in load spike situations for example.

tbdr 12y ago

I was able to crash the system without even trying. After waiting for a 500MB something docker image download and running the container halted the host OSX machine while looping with errors (failed API connections, failed to load SIGAR, ...) The screenshots looked great but the first steps experience were a deal breaker.

real_joschi 12y ago
We've tested the Docker image on Mac OS X with boot2docker but of course there are always things that can go wrong. It would be awesome if you could help us improve the Docker image by creating an issue at https://github.com/Graylog2/graylog2-images/issues https://github.com/Graylog2/graylog2-images/issues with the error messages you've encountered when starting the container.
nonane 12y ago
I just tried this with boot2docker on a OS X machine (Yosemite) and it went very smoothly.
deleted 12y ago
[deleted]
teacup50 12y ago
Maybe requiring a full VM when a standalone self-contained application will do is not the winning strategy.
- real_joschi 12y ago
  Oh, we got both kinds. We got country and western. ;-) Seriously, the Docker image and the VM images are there to help people getting started and to quickly try out Graylog. We also offer regular OS packages in DEB and RPM formats (supporting Debian 7, Ubuntu 12.04 and 14.04, and CentOS 6) and a quick setup application (for a simple demo setup of Graylog and its dependencies). So choose your poison and be happy!