March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2451) FD_ALL3: improvements over FD_ALL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2451?page=com.atlassian.jira.plugin... ] Bela Ban edited comment on JGRP-2451 at 3/5/20 4:21 AM: -------------------------------------------------------- [~dan.berindei]This sound like a good solution, but I guess you meant timeout=60s in your example, didn't you? I changed that in your algorithm above was (Author: belaban): [~dan.berindei]This sound like a good solution, but I guess you meant timeout=60s in your example, didn't you? > FD_ALL3: improvements over FD_ALL > --------------------------------- > > Key: JGRP-2451 > URL: https://issues.redhat.com/browse/JGRP-2451 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.1 > > > Improvements to {{FD_ALL}}. > * Messages should count as heartbeats ({{msg_counts_as_heartbeat}} should be *default*, and as such, deprecated/removed). > * When a multicast message is sent before {{interval}} elapsed, we suppress sending a heartbeat > It is crucial that setting the in the map is quick, especially since this is done on every message. This should not be an issue, as we fetch the current time from the time service, which does *not* call {{System.nanoTime()}} or {{System.currentTimeMillis()}} every time. > The advantage is that we only send heartbeats when there is no (multicast) traffic, and we don't suspect a member P when heartbeats have been missing despite receiving traffic from P. > We need to think about whether to consider unicast messages, too, on the sender side: we could populate a bit map with messages sent to members: on a unicast message to P, P's bit would be set in the bit. On a multicast message, all bits would be set. Then, we could selectively send heartbeats only to members with bits set to 0. > However, this is only feasible with sending a message N-1 times (e.g. TCP); for UDP we don't have such an 'anycast' available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2451) FD_ALL3: improvements over FD_ALL

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2451?page=com.atlassian.jira.plugin... ] Bela Ban edited comment on JGRP-2451 at 3/5/20 4:20 AM: -------------------------------------------------------- I propose something like {{FD_ALL2}}, but with {{N=timeout/interval}} bits per member # Every time the timer task runs: ## If all N bits are 0, suspect the member ## Increment the bit index ## Set the current bit to 0 # Every time a message is received: ## Set the current bit to 1 E.g. with timeout=60s and interval=20s, N=3 bits # Start at time T with all bits set # At time T+20s, all bits are set, and the timer sets bit(1) = 0 # At any time between T+20 and T+40, a message arrives, and it sets bit(1) = 1 # At time T+40s, the timer sets bit(2) = 0 # At time T+60s, the timer sets bit(0) = 0 # At time T+80s, the timer sets bit(1) = 0 # At time T+100s, the timer finally sees that all bits are 0 and suspects the node Thus the time between the last heartbeat and the node being suspected is between 60s and 80s. was (Author: dan.berindei): I propose something like {{FD_ALL2}}, but with {{N=timeout/interval}} bits per member # Every time the timer task runs: ## If all N bits are 0, suspect the member ## Increment the bit index ## Set the current bit to 0 # Every time a message is received: ## Set the current bit to 1 E.g. with timeout=3s and interval=20s, N=3 bits # Start at time T with all bits set # At time T+20s, all bits are set, and the timer sets bit(1) = 0 # At any time between T+20 and T+40, a message arrives, and it sets bit(1) = 1 # At time T+40s, the timer sets bit(2) = 0 # At time T+60s, the timer sets bit(0) = 0 # At time T+80s, the timer sets bit(1) = 0 # At time T+100s, the timer finally sees that all bits are 0 and suspects the node Thus the time between the last heartbeat and the node being suspected is between 60s and 80s. > FD_ALL3: improvements over FD_ALL > --------------------------------- > > Key: JGRP-2451 > URL: https://issues.redhat.com/browse/JGRP-2451 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0, 4.2.1 > > > Improvements to {{FD_ALL}}. > * Messages should count as heartbeats ({{msg_counts_as_heartbeat}} should be *default*, and as such, deprecated/removed). > * When a multicast message is sent before {{interval}} elapsed, we suppress sending a heartbeat > It is crucial that setting the in the map is quick, especially since this is done on every message. This should not be an issue, as we fetch the current time from the time service, which does *not* call {{System.nanoTime()}} or {{System.currentTimeMillis()}} every time. > The advantage is that we only send heartbeats when there is no (multicast) traffic, and we don't suspect a member P when heartbeats have been missing despite receiving traffic from P. > We need to think about whether to consider unicast messages, too, on the sender side: we could populate a bit map with messages sent to members: on a unicast message to P, P's bit would be set in the bit. On a multicast message, all bits would be set. Then, we could selectively send heartbeats only to members with bits set to 0. > However, this is only feasible with sending a message N-1 times (e.g. TCP); for UDP we don't have such an 'anycast' available. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13198) Upgrade MicroProfile Metrics 2.3

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13198?page=com.atlassian.jira.plugi... ] Ingo Weiss reassigned WFLY-13198: --------------------------------- Assignee: Daniel Kreling (was: Jeff Mesnil) > Upgrade MicroProfile Metrics 2.3 > -------------------------------- > > Key: WFLY-13198 > URL: https://issues.redhat.com/browse/WFLY-13198 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Metrics > Affects Versions: 7.3.0.GA > Reporter: Ingo Weiss > Assignee: Daniel Kreling > Priority: Major > Labels: MP3.3 > Fix For: 7.3.1.GA > > > This also includes upgrade of smallrye-metrics that implements MP Metrics 2.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13198) Upgrade MicroProfile Metrics 2.3

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13198: --------------------------------- Summary: Upgrade MicroProfile Metrics 2.3 Key: WFLY-13198 URL: https://issues.redhat.com/browse/WFLY-13198 Project: WildFly Issue Type: Component Upgrade Components: MP Metrics Reporter: Ingo Weiss Assignee: Jeff Mesnil Fix For: 19.0.0.Beta3, 20.0.0.Beta1 This also includes upgrade of smallrye-metrics that implements MP Metrics 2.3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13197) Upgrade SmallRye JWT to 2.0.13

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13197: --------------------------------- Summary: Upgrade SmallRye JWT to 2.0.13 Key: WFLY-13197 URL: https://issues.redhat.com/browse/WFLY-13197 Project: WildFly Issue Type: Component Upgrade Components: MP JWT Reporter: Ingo Weiss Assignee: Darran Lofthouse Fix For: 19.0.0.Beta3, 20.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13197) Upgrade SmallRye JWT to 2.0.13

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13197?page=com.atlassian.jira.plugi... ] Ingo Weiss reassigned WFLY-13197: --------------------------------- Assignee: Daniel Kreling (was: Darran Lofthouse) > Upgrade SmallRye JWT to 2.0.13 > ------------------------------ > > Key: WFLY-13197 > URL: https://issues.redhat.com/browse/WFLY-13197 > Project: WildFly > Issue Type: Component Upgrade > Components: MP JWT > Affects Versions: 7.3.0.GA > Reporter: Ingo Weiss > Assignee: Daniel Kreling > Priority: Major > Labels: MP3.3 > Fix For: 7.3.1.GA > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2459) SWIM: new failure detection protocol

by Bela Ban (Jira)

Bela Ban created JGRP-2459: ------------------------------ Summary: SWIM: new failure detection protocol Key: JGRP-2459 URL: https://issues.redhat.com/browse/JGRP-2459 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 [1] www.cs.cornell.edu/projects/Quicksilver/public_pdfs/SWIM.pdf -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2769) callback methods for: before/after invoke BKM/DS

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-2769?page=com.atlassian.jira.plug... ] Toshiya Kobayashi commented on DROOLS-2769: ------------------------------------------- This JIRA will implement only beforeInvokeBKM/afterInvokeBKM because beforeEvaluateDecisionService/afterEvaluateDecisionService had already worked for before/after the "actual execution". > callback methods for: before/after invoke BKM/DS > ------------------------------------------------ > > Key: DROOLS-2769 > URL: https://issues.redhat.com/browse/DROOLS-2769 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > {quote}As part of another feature, I would like to create callback methods for both "before/after invoke BKM/DS", so that we can report on actual execution of BKMs and Decision Services. But this is a conversation for another day.{quote} > Ref https://github.com/kiegroup/drools/pull/1986#discussion_r204029977 > Augment Listener and implement callbacks when invoking BKM and Decision Service(s) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13196) Upgrade smallrye-fault-tolerance to 4.1.1

by Ingo Weiss (Jira)

Ingo Weiss created WFLY-13196: --------------------------------- Summary: Upgrade smallrye-fault-tolerance to 4.1.1 Key: WFLY-13196 URL: https://issues.redhat.com/browse/WFLY-13196 Project: WildFly Issue Type: Task Components: MP Fault Tolerance Reporter: Ingo Weiss Assignee: Radoslav Husar Fix For: 19.0.0.Beta3, 20.0.0.Beta1 Brings in a couple of fixes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13196) Upgrade smallrye-fault-tolerance to 4.1.1

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13196?page=com.atlassian.jira.plugi... ] Ingo Weiss reassigned WFLY-13196: --------------------------------- Assignee: Daniel Kreling (was: Radoslav Husar) > Upgrade smallrye-fault-tolerance to 4.1.1 > ----------------------------------------- > > Key: WFLY-13196 > URL: https://issues.redhat.com/browse/WFLY-13196 > Project: WildFly > Issue Type: Task > Components: MP Fault Tolerance > Reporter: Ingo Weiss > Assignee: Daniel Kreling > Priority: Major > Fix For: 19.0.0.Beta3, 20.0.0.Beta1 > > > Brings in a couple of fixes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2020