January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2421) Don't log an IllegalArgumentException when receiving an invalid delta view

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2421?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2421: --------------------------- Fix Version/s: 4.2.0 (was: 4.1.9) > Don't log an IllegalArgumentException when receiving an invalid delta view > -------------------------------------------------------------------------- > > Key: JGRP-2421 > URL: https://issues.redhat.com/browse/JGRP-2421 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 4.1.6 > Reporter: Dan Berindei > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.0 > > > When the cluster is unstable but not because of the network (e.g. excessive load and long GC pauses), a suspected node can keep receiving view updates long after it was excluded from the view. > The first view triggers a warning about not being a member, but because later delta-views cannot be reconstructed, their warnings look much worse, even though they're about the same thing. > {noformat} > 11:31:05,281 WARN [org.jgroups.protocols.pbcast.GMS] (jgroups-79,edg-perf03-47882) edg-perf03-47882: not member of view [edg-perf01-21541|6]; discarding it > 11:31:16,267 WARN [org.jgroups.protocols.pbcast.GMS] (jgroups-80,edg-perf03-47882) edg-perf03-47882: failed to create view from delta-view; dropping view: java.lang.IllegalStateException: the view-id of the delta view ([edg-perf01-21541|6]) doesn't match the current view-id ([edg-perf01-21541|5]); discarding delta view [edg-perf01-21541|7], ref-view=[edg-perf01-21541|6], left=[edg-perf06-47720] > {noformat} > Maybe GMS could keep track of when it receives a view in which it is not a member and stop processing delta views from that node? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2401) Version number for configuration

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2401?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2401: --------------------------- Fix Version/s: 4.2.0 (was: 4.1.9) > Version number for configuration > -------------------------------- > > Key: JGRP-2401 > URL: https://issues.redhat.com/browse/JGRP-2401 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.0 > > > Add a version to the config, which corresponds with the JGroups version. > At startup, if the JGroups version and the confi version don't match, issue a warning. Possibly don't start if the major version differs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2403) Dump information in panic scenarios

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2403?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2403: --------------------------- Fix Version/s: 4.2.0 (was: 4.1.9) > Dump information in panic scenarios > ----------------------------------- > > Key: JGRP-2403 > URL: https://issues.redhat.com/browse/JGRP-2403 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.0 > > > When there is a panic situation (e.g. thread pool exhausted), dump information to a file at FATAL level. > Also dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default, e.g. in Infinispan. > These files can be sent to support via an SOS report. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2412) GMS: reduce likelyhood of merges on concurrent new member startup

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2412?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2412: --------------------------- Fix Version/s: 4.2.0 (was: 4.1.9) > GMS: reduce likelyhood of merges on concurrent new member startup > ----------------------------------------------------------------- > > Key: JGRP-2412 > URL: https://issues.redhat.com/browse/JGRP-2412 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.0 > > > When multiple new members are started concurrently, and no coord is present yet, different clients get different discovery results, and this may lead to merging. > If we have no coord, we could run the discovery protocol multiple time, *with the current members list being cached*, and then might end up with a more similar list of new members. > This could be governed by an additional attribute in {{Discovery}} ({{num_discovery_runs}}?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2402) SOS report

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2402?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2402: --------------------------- Fix Version/s: 4.2.0 (was: 4.1.9) > SOS report > ---------- > > Key: JGRP-2402 > URL: https://issues.redhat.com/browse/JGRP-2402 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.0 > > > Add the ability to dump the most important attributes to a file / log (configurable), e.g.: > * Max threads > * Number of rejected messages > * Size of retransmission tables (NAKACK2, UNICAST3) > This can be used to diagnose issues by telling the customer to invoke this command and attach the resulting file to a ticket -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2406) MERGE3 not working with TCP using ForkJoinPool

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2406?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2406: --------------------------- Fix Version/s: 4.2.0 (was: 4.1.9) > MERGE3 not working with TCP using ForkJoinPool > ---------------------------------------------- > > Key: JGRP-2406 > URL: https://issues.redhat.com/browse/JGRP-2406 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.1.8 > Reporter: Olivier Peyrusse > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.0 > > Attachments: logs.tgz, project.zip, timeline.txt > > > With JDK11, using the TCP protocol with the ForkJoinPool is causing constant failures of MERGE3. > I consistently observed the following, from the point of view of a member M > - M asks for other coordinator views. It contacts A and B > - A and B send their views > - M waits and timeouts for receiving views and abort the merge > - immediately after aborting the merge, M process messages containing the views of A and B. > In [^timeline.txt], you will see the extracts for logs from the various members at play. > After many experiments, the one parameter causing this issue is in the TCP protocol. > {code:xml} > <TCP > ... > thread_pool.use_fork_join_pool="true" /> > {code} > Setting {{thread_pool.use_fork_join_pool}} to true repeatedly produces the problem, while using {{thread_pool.use_fork_join_pool}} with false works fine. > Project details: > - as tested within Kubernetes, this project uses KUBE_PING as its discovery protocol > - to understand the reason for the failed merges, I created the protocol MERGE4, that is MERGE3 with additional logs. > - [^logs.tgz] contains all logs from the various members involved in the test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2374) TCP/TCP_NIO2: add TLS

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2374?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2374: --------------------------- Fix Version/s: 4.2.0 (was: 4.1.9) > TCP/TCP_NIO2: add TLS > --------------------- > > Key: JGRP-2374 > URL: https://issues.redhat.com/browse/JGRP-2374 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.0 > > > Add TLS to the TCP and TCP_NIO2 transports. Look into wildfly-openssl [1] for the impl. > [1] https://github.com/wildfly-security/wildfly-openssl -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12880) Upgrade Jaeger client to 0.34.1

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12880?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12880: --------------------------------- Labels: downstream_dependency (was: ) > Upgrade Jaeger client to 0.34.1 > ------------------------------- > > Key: WFLY-12880 > URL: https://issues.redhat.com/browse/WFLY-12880 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenTracing > Affects Versions: 18.0.1.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Labels: downstream_dependency > Fix For: 19.0.0.Beta1 > > > Upgrade Jaeger client to 1.1.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4882) [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4882?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-4882: -------------------------------- Affects Version/s: 7.31.0.Final > [Guided DecisionTable] Incorrect getters and setters for fields that starts with one lowercase letter > ----------------------------------------------------------------------------------------------------- > > Key: DROOLS-4882 > URL: https://issues.redhat.com/browse/DROOLS-4882 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Decision Tree Editor, Guided Rule Editor, Guided Score Card Editor, Guided Template Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: reported-by-qe > > If the guided decision table uses fact field that has form 'xXxxx' then the generated getters and setters are incorrect. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12944) (7.3.z) Upgrade Jaeger client to 0.34.1

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-12944: ------------------------------------ Summary: (7.3.z) Upgrade Jaeger client to 0.34.1 Key: WFLY-12944 URL: https://issues.redhat.com/browse/WFLY-12944 Project: WildFly Issue Type: Component Upgrade Components: MP OpenTracing Affects Versions: 18.0.1.Final Reporter: Ilia Vassilev Assignee: Emmanuel Hugonnet Fix For: 19.0.0.Beta1 Upgrade Jaeger client to 1.1.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 January 2020