Commits

commits@lists.kronosnet.org

2 participants
33123 discussions

libqb-build-all-nonvoting - Build # 194 - Failure!
by jenkins＠kronosnet.org 09 Sep '19

09 Sep '19

libqb-build-all-nonvoting - Build # 194 - Failure: Check console output at https://ci.kronosnet.org/job/libqb-build-all-nonvoting/194/ to view the results.

1 10

knet-build-all-voting - Build # 1436 - Failure!
by jenkins＠kronosnet.org 09 Sep '19

09 Sep '19

knet-build-all-voting - Build # 1436 - Failure: Check console output at https://ci.kronosnet.org/job/knet-build-all-voting/1436/ to view the results.

1 1

[kronosnet/kronosnet] f45e4c: [pmtud] switch to use async version of dstcache up...
by Fabio M. Di Nitto 09 Sep '19

09 Sep '19

Branch: refs/heads/lock-fix Home: https://github.com/kronosnet/kronosnet Commit: f45e4c67902b95bcd212275f5f6081fa31311793 https://github.com/kronosnet/kronosnet/commit/f45e4c67902b95bcd212275f5f608… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2019-09-09 (Mon, 09 Sep 2019) Changed paths: M libknet/threads_pmtud.c Log Message: ----------- [pmtud] switch to use async version of dstcache update due to locking context (read vs write) Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>

1 0

pacemaker-build-all-voting - Build # 1613 - Failure!
by jenkins＠kronosnet.org 09 Sep '19

09 Sep '19

pacemaker-build-all-voting - Build # 1613 - Failure: Check console output at https://ci.kronosnet.org/job/pacemaker-build-all-voting/1613/ to view the results.

1 0

pacemaker-build-all-voting - Build # 1610 - Failure!
by jenkins＠kronosnet.org 09 Sep '19

09 Sep '19

pacemaker-build-all-voting - Build # 1610 - Failure: Check console output at https://ci.kronosnet.org/job/pacemaker-build-all-voting/1610/ to view the results.

1 0

knet-build-all-nonvoting - Build # 1232 - Failure!
by jenkins＠kronosnet.org 09 Sep '19

09 Sep '19

knet-build-all-nonvoting - Build # 1232 - Failure: Check console output at https://ci.kronosnet.org/job/knet-build-all-nonvoting/1232/ to view the results.

1 0

[kronosnet/kronosnet]
by kronosnet CI bot 09 Sep '19

09 Sep '19

Branch: refs/heads/coverity_scan Home: https://github.com/kronosnet/kronosnet

1 0

[kronosnet/kronosnet]
by Fabio M. Di Nitto 09 Sep '19

09 Sep '19

Branch: refs/heads/functional-testing Home: https://github.com/kronosnet/kronosnet

1 0

[kronosnet/kronosnet]
by Fabio M. Di Nitto 09 Sep '19

09 Sep '19

Branch: refs/heads/latency-fixes Home: https://github.com/kronosnet/kronosnet

1 0

[kronosnet/kronosnet] 4df82e: [links] stabilize latency calculation when nodes a...
by Fabio M. Di Nitto 09 Sep '19

09 Sep '19

Branch: refs/heads/stable1-proposed Home: https://github.com/kronosnet/kronosnet Commit: 4df82e5fd847423b164f4fba70e20fd0026639ce https://github.com/kronosnet/kronosnet/commit/4df82e5fd847423b164f4fba70e20… Author: Fabio M. Di Nitto <fdinitto(a)redhat.com> Date: 2019-09-09 (Mon, 09 Sep 2019) Changed paths: M libknet/threads_heartbeat.c M libknet/threads_rx.c Log Message: ----------- [links] stabilize latency calculation when nodes are not responsive The following scenario is more of a corner case than normal, but this change allows to better deal with this situation: 1) 2 nodes cluster (corosync) (node A and node B) 2) kill -stop $(pidof corosync) on node A 3) node B will continue to send ping packets to node A 4) node A is accumulating those ping packets in the kernel network socket 5) wait some seconds and unpause node A 6) node A will start processing the ping packets in the queue and send pong replies to node B 7) node B will see an extreme increase of latency due those "obsoleted" ping/pong packets 8) node B, as latency increases, will take longer and longer to notice that node A is down due to the pong_timeout adjustment for latency (required for initial cluster spike). the solution: 1) Use average latency to calculate pong_timeout_adj vs latency_max. Averate latency will go down again in time, while latency_max is never reset. 2) RX thread will filter out all pong packets that have higher latency than currently configure pong_timeout. This barrier should have been in place even before. this solution reduces the latency spike on node B to a perfectly reasonable level and it will all eventually stabilize over time as latency samples increase and latency will reduce. Please be aware that using a pong_timeout smaller than latency will simply mark the link down now. Signed-off-by: Fabio M. Di Nitto <fdinitto(a)redhat.com>

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

Commits