[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:
---------------------------
Affects Version/s: 5.0.0.Alpha3
Fix Version/s: (was: 5.0)
(was: 4.2.2)
> Dump information in panic scenarios
> -----------------------------------
>
> Key: JGRP-2403
> URL: https://issues.redhat.com/browse/JGRP-2403
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 5.0.0.Alpha3
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
>
> When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) 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, 1 month
[JBoss JIRA] (JGRP-2430) GossipRouter: more efficient routing
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2430?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2430:
---------------------------
Affects Version/s: 5.0.0.Alpha3
Fix Version/s: (was: 5.0)
(was: 4.2.2)
> GossipRouter: more efficient routing
> ------------------------------------
>
> Key: JGRP-2430
> URL: https://issues.redhat.com/browse/JGRP-2430
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.0.Alpha3
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
>
> GossipRouter supports both NIO (ByteBuffer) and TCP (stream-based) connections. In both cases, however, the entire message is read and then routed to the destination address.
> It would be better to only read the cluster name and target address, and then use efficient stream-to-stream (or channel-to-channel) _transfer mechanisms_, which avoids temporary copies of data and the full reading of messages.
> Also look into routing of entire message _batches_.
> Investigate whether this is possible.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[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:
---------------------------
Affects Version/s: 5.0.0.Alpha3
Fix Version/s: (was: 5.0)
(was: 4.2.2)
> SOS report
> ----------
>
> Key: JGRP-2402
> URL: https://issues.redhat.com/browse/JGRP-2402
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 5.0.0.Alpha3
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
>
> 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, 1 month
[JBoss JIRA] (JGRP-2412) GMS: reduce likelihood 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:
---------------------------
Affects Version/s: 5.0.0.Alpha3
Fix Version/s: (was: 5.0)
(was: 4.2.2)
> GMS: reduce likelihood of merges on concurrent new member startup
> -----------------------------------------------------------------
>
> Key: JGRP-2412
> URL: https://issues.redhat.com/browse/JGRP-2412
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.0.Alpha3
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
>
> 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, 1 month