Is somebody having the same problem? Does the 2.9.2 solve this issue for anyone?Thanks & regards,
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Last Friday, I also upgraded our production server to 2.9.2. Right now, checked the SSH-Stream-Workerthreads and 2 out of 10 are already stuck.
Hello everyone,We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).
Gerrit: 2.9.2Jenkins: 1.580.1Gerrit Plugin: 2.12.0
Am Montag, 15. Dezember 2014 12:14:27 UTC+1 schrieb Marcelo Ávila:Hello everyone,We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).Can you define so far (in hours)?
Gerrit: 2.9.2Jenkins: 1.580.1 <= from 1.532.2Gerrit Plugin: 2.12.0 <= from 2.11.0
2014-12-15 9:19 GMT-02:00 David Ostrovsky <david.o...@gmail.com>:
Am Montag, 15. Dezember 2014 12:14:27 UTC+1 schrieb Marcelo Ávila:Hello everyone,We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).Can you define so far (in hours)?We had a Gerrit auto restart running every day (3AM) to live with this issue, but last week we noticed the issue was not happening anymore, I mean, the SSH threads were not getting stuck during the day, so we disabled the Gerrit auto restart on this weekend (the last one was executed on 13-Dec).
Gerrit: 2.9.2Jenkins: 1.580.1 <= from 1.532.2Gerrit Plugin: 2.12.0 <= from 2.11.0Interesting. What have you changed in your setup and from what version?
--
On Mon, Dec 15, 2014 at 1:07 PM, Marcelo Ávila <mav...@cpqd.com.br> wrote:2014-12-15 9:19 GMT-02:00 David Ostrovsky <david.o...@gmail.com>:
Am Montag, 15. Dezember 2014 12:14:27 UTC+1 schrieb Marcelo Ávila:Hello everyone,We have good news from the front... after a complete upgrade of our "defective" Jenkins server, apparently the SSH threads issue is gone (so far at least).Can you define so far (in hours)?We had a Gerrit auto restart running every day (3AM) to live with this issue, but last week we noticed the issue was not happening anymore, I mean, the SSH threads were not getting stuck during the day, so we disabled the Gerrit auto restart on this weekend (the last one was executed on 13-Dec).How many SSH-Stream-Worker threads do you have?
2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:How many SSH-Stream-Worker threads do you have?20
2014-12-15 13:00 GMT-02:00 Marcelo Ávila <mav...@cpqd.com.br>:2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:How many SSH-Stream-Worker threads do you have?20Just to be sure, each one of those threads are connected to a different Jenkins server
On Mon, Dec 15, 2014 at 5:01 PM, Gustavo Leite de Mendonça Chaves <gus...@cpqd.com.br> wrote:2014-12-15 13:00 GMT-02:00 Marcelo Ávila <mav...@cpqd.com.br>:2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:How many SSH-Stream-Worker threads do you have?20Just to be sure, each one of those threads are connected to a different Jenkins serverAFAIK, it is NOT one thread per connection... and you don't need one thread per one Jenkins server.As long as there are unblocked threads the events will be streamed to all Jenkins servers.
2014-12-15 14:15 GMT-02:00 Saša Živkov <ziv...@gmail.com>:On Mon, Dec 15, 2014 at 5:01 PM, Gustavo Leite de Mendonça Chaves <gus...@cpqd.com.br> wrote:2014-12-15 13:00 GMT-02:00 Marcelo Ávila <mav...@cpqd.com.br>:2014-12-15 12:34 GMT-02:00 Saša Živkov <ziv...@gmail.com>:How many SSH-Stream-Worker threads do you have?20Just to be sure, each one of those threads are connected to a different Jenkins serverAFAIK, it is NOT one thread per connection... and you don't need one thread per one Jenkins server.As long as there are unblocked threads the events will be streamed to all Jenkins servers.I'm sorry. I meant we see 20 connections (not threads) with the "ssh gerrit gerrit show-connections" command. Most of them are to the machines where we have our Jenkins servers running. Using "lsof -i :29418" on each of those machines we can see that each Jenkins server (a java process) has a single connection to Gerrit, while before we had one of those Jenkins servers which would accumulate multiple SSH connections to Gerrit over time.How can I count those SSH-Stream-Worker threads? I tried using "jstack -F PID" to generate a thread dump from Gerrit but I couldn't find the string "SSH-Stream-Worker" anywhere in its output.
Any further update on this?which gerrit/jenkins/gerrit-trigger version solves this problem completely?