I've installed Neo4J 3.2.1 server on an Ubuntu 14.04 machine with 16G of RAM. I'm connecting to this Neo4J server from my Windows 10 laptop via browser (http://server_ip_address:7474).
I'm working with 3 different graphs with 280MB, 6MB and 13MB. No problem when I activate one of the two smaller ones but impossible to work (make cypher queries in the NEO4J-browser) with the larger because it blocks for long periods (over one minute each).
I've tried to fix this myself. Read https://neo4j.com/docs/operations-manual/current/performance/ and set the following values in neo4j.conf file: - dbms.memory.heap.initial_size=12g; - dbms.memory.heap.max_size=12g; - dbms.memory.pagecache.size=4g.
I also tried: - echo noop > /sys/block/sda/queue/scheduler; - mount -o remount,noatime /.
Since none of these attempts worked, I would appreciate some help!
I'm not sure but it seems that there's some kind of cyclic script running causing the delays.
I only have trouble using the http browser server. I wrote a simple java application to make remote queries without using the http browser, produced a executable jar with it and when I run that jar and make the queries the response times are normal.
Related
I am running some services with Google Cloud Run. While performance has been satisfactory, there's a recurrent issue with extremely slow startup time, which leads to occasionally dropped requests when new containers can't spin up in time.
Currently, with first gen execution environments and startup CPU boost enabled, Google's dashboard reports around 18 to 50 seconds of startup time. Image is based on ruby:3.0.2, and it runs a Ruby on Rails 6 application. In a development environment, startup (timed from run to container accepting requests) never seems to take more than 5 seconds.
I want to know what tools are available to diagnose this issue, and if there are any obvious pitfalls with my specific case that I might be missing.
I've tried playing around with the service's configuration options, to no avail. The biggest suspect is a startup bash script that handles migrations on the first boot, and asset compiling on development. However, I've tried building with an empty script, and the problem persists. I also think the container images might be too large (around 700Mb), but I haven't gotten around to slimming then down nor found evidence that this is the problem.
I'm running Neo4j 3.2.6 on CENTOS 6.9. I have two problems:
First, Neo4j keeps stopping (typically about 5 times per day). There is nothing in the debug.log at the time of the failure (although there are many lines from the time I restart the service). How can I identify the problem? Which log files would give me a clue to the problem? Happy to share log files here if someone tells me which files to share.
Second, the above problem is compounded by the fact that I can't get Neo4j to restart automatically when it fails. I believe CENTOS 6.9 uses Upstart but I'm not having much luck setting this up. How do I set up Neo4j to restart on failure in CENTOS 6.9?
I have upgraded Cacti from 0.8.7g to 0.8.8a. (We use poller not spine).
I followed the upgrade instructions here - http://docs.cacti.net/manual:088:1_installation.3_upgrading#upgrading_cacti
Cacti Server; Linux RedHat server RHEL4connect to mysql
Not using custom scripts basically inbuilt server (index) scripts.
What doesnt graph is hard drive usage (hdtotal/hdfreespace) on windows or linux boxes
Windows servers will only graph network stats not hd/cpu.
I have confirmed that the OID in the Server script directory are correct. Went through the trouble shooting steps here - http://docs.cacti.net/manual:088:4_help.2_debugging#debugging
Linux server are ok with recording and displaying cpu/network but not hard drive data.
I realise this post is a bit all over the place, but new to cacti and want to fix these issues. Any information/help is appreciated. Even if it is just to set up a windows server monitoring graph.
Thanks
Roger
Did you rebuild the poller cache already ?
Go to Console -> System Utilities -> Rebuild Poller Cache
That rebuilds the cache which the poller is using. It sometimes get's not updated properly during an update leaving some graphs empty.
FYI
We had no luck with this upgrade and ended up rebuilding the server using packages available through redhat repositories.
Thanks for reading
I'm using Grails 2.0.4 and elasticsearch 0.19.8, with a homegrown build of the elasticsearch-grails plugin to use 0.19.8, running on a micro Ubuntu instance of EC2.
I'm building my grails project locally as a war. When I drop this was in a jetty container locally (on my laptop), jetty starts and I'm able to navigate to the root context (as expected) and get my site.
However, when I take the same war (confirmed via md5sum) in the same version of jetty (confirmed via md5sum) on a micro EC2 instance, I get strange results.
Occasionally, jetty starts and my application is available...all is well. But then other times, jetty won't start...and the logs are complaining about elasticsearch.
Now, I'm the first to admit that running both elasticsearch and jetty (with a grails war) on the same node is, well, not the greatest idea...but, this is a test environment, and I'm okay with swapping to disk (not a perf testing lab).
But, what's driving me batty is the inconsistency in running my application. Currently, I cannot get it to start (which, I suppose, counters my "inconsistency" argument). But even taking a "starting" war, with MINIMAL changes in the war (no domain object changes, just changes in controller and/or view), my app won't start - complaining about elasticsearch.
Here's the gist
In the past, I've solved this by stopping elasticsearch, and blowing away /var/lib/elasticsearch/elasticsearch (which is basically, as I understand it, a crude way of blowing away the elasticsearch index).
But now, this doesn't appear to be working. Neither does uninstall/reinstall elasticsearch.
Can anybody offer any advice on what to look for and/or where to look?
Ok, this is driving my crazy, but I found an answer.
/data contains an elasticsearch directory which, apparently, had bad data...I deleted this directory and restarted jetty and...
Viola!
I have NO idea how it got into this state, nor the actual ramifications of deleting the directory (I think elasticsearch data is persisted in the elasticsearch node...)
I suspect an incomplete shutdown of my app...
Thanks for everybody's input.
Recently I configured my instance into a micro environment in EC2 with glassfish and mysql in windows..
I deployed my war and i was able to access my site through http.
I changed my application and redeployed the war and it also worked.
When I was about to redeploy the war for 4th or 5th time, the application got deployed, I saw the message in the log file. But I was unable to access the site through http.
Then I tried the command "asadmin list-applications" and I got the following message.
Error occurred during initialization of VM
Could not reserve enough space for object heap
After that I was not able to connect to my instance through RDP and I had to reboot, I was able to access it again after that. I started the servers again (glassfish mysql), but no luck.
I noticed that the memory usage is around 90% or more. CPU isage is low.
now I can not access my site through http. what shall i do ?
Thanks in advance !
Honestly, there are a couple issues working against you here:
1) Windows requires FAR more RAM than Ubuntu to run at a minimum decent level.
2) GlassFish has a much larger footprint than Tomcat or Jetty.
Is there any particular reason you need Windows? Like is there a specific need that your server run some executables for file processing or something like that outside the JVM? Most would agree that Linux (Ubuntu or other) will give you much better results in performance and stability to run an App Server like GlassFish in any environment.