I will look into it and get back to you!
Best Regards
Matthew Lowe
> On 03 Jun 2016, at 22:24, Jacob Johansen wrote:
>
> Is the server the client is trying to connect to listening on the
> port. (netstat command)
>
> Is your DNS or host file correct?
> Jacob Johansen
>
than you very much for sharing these. i hope that others will contribute.
regards,
florin
On Friday, June 3, 2016, Stephen Powis wrote:
> Here's the flags we're using:
>
> -Xms3G -Xmx3G -XX:MaxPermSize=100M -Xloggc:gc-%ID%.log
> -XX:+PrintGCDateStamps -XX:+PrintGCDetails
Giving this a bump, as its rather important.
To be more specific, no traffic ever goes through the topology. As soon as it
it started, the error will start.
One time I left it overnight and it connected, but I am unsure how long this
took to happen.
And ideas would be great, thanks!
> On 03
Here's the flags we're using:
-Xms3G -Xmx3G -XX:MaxPermSize=100M -Xloggc:gc-%ID%.log
-XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintTenuringDistribution
-XX:+PrintGCApplicationStoppedTime -XX:+DisableExplicitGC
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=50M
Hi,
+1 for G1 for large heaps where you are seeing big GC pauses. Works well
for us.
See:
https://sematext.com/blog/2013/06/24/g1-cms-java-garbage-collector/
Otis
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training -
Hello all,
I have just updated my cluster.xml to use some appenders that I made.
I am now getting items like the following in the logs.
I seems like given enough time (hours), it will eventually resolve and
start to work.
I am running storm 0.9.4
2016-06-03T13:46:28.825+ b.s.m.n.Client