[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.2
5.0.0.Alpha4
Affects Version/s: (was: 5.0.0.Alpha4)
> 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.2, 5.0.0.Alpha4
>
>
> 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-815) Scatter/Gather to avoid copying
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-815?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-815:
--------------------------
Affects Version/s: 5.0.0.Alpha3
Fix Version/s: (was: 5.0)
> Scatter/Gather to avoid copying
> -------------------------------
>
> Key: JGRP-815
> URL: https://issues.redhat.com/browse/JGRP-815
> Project: JGroups
> Issue Type: Sub-task
> Affects Versions: 5.0.0.Alpha3
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Attachments: bla10.java, bla9.java
>
>
> When we invoke Channel.send(), we pass a bufffer to JGroups. At the transport level, JGroups marshals the sender and destination address, plus all headers and the buffer into a new byte[] buffer, which is then passed to the socket (DatagramSocket, MulticastSocket, Socket).
> We cannot do gathering writes on a DatagramSocket because DatagramSocket doesn't expose this functionality, contrary to a DatagramChannel.
> We could avoid having to copy the user's buffer by using gathering writes: effectively passing to the socket NIO ByteBuffers containing:
> 1: Src and dest address plus flags, plus possibly size
> 2: The marshalled headers
> 3: The buffer passed to JGroups by the user
> We can obtain a gathering-write channel as follows:
> ByteBuffer[] buffers; // contains the 3 byte buffers above
> DatagramSocket sock;
> DatagramChannel ch=sock.getChannel();
> ch.write(buffers, 0, length); // length is the number of bytes of the total marshalled message
> This is supported by a GatheringByteChannel.
> I don't think there's currently a need to do scattered reads, but this needs to get investigated more. Also investigate whether MulticastSockets support gathering writes (whether they expose the correct DatagramChannel).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JGRP-809) Copyless stack
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-809?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-809:
--------------------------
Affects Version/s: 5.0.0.Alpha3
Fix Version/s: (was: 5.0)
> Copyless stack
> --------------
>
> Key: JGRP-809
> URL: https://issues.redhat.com/browse/JGRP-809
> Project: JGroups
> Issue Type: Feature Request
> Affects Versions: 5.0.0.Alpha3
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Attachments: Buf.java, BufAllocator.java, Message.java
>
>
> Currently (as of 2.7), the transport reads the contents of a received packet into a buffer, then passes a *copy* of the buffer to a thread from the OOB or incoming thread pools. To prevent this copy, we can
> - have the receiver read only the version and OOB flag (to see which thread pool to dispatch the packet to)
> - pass a ref to the socket to a thread from the incoming of OOB pool, have that thread read the packet and return
> - each thread in the pool has its own buffer into which the buffer is read from the socket
> Possibly use NIO: we can install a selector and get woken up whenever data to be read is present. At that point, we can pass the ref to the socket to the handler thread and return immediately. NIO with channels for multicast sockets is available only in JDK 7 (or 8?), so this is a bit off... However, we can already implement this with reading the version and flags bytes and then passing the socket to the handler
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JGRP-2457) Make time and byte values more legible
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2457?page=com.atlassian.jira.plugin... ]
Bela Ban updated JGRP-2457:
---------------------------
Affects Version/s: 5.0.0.Alpha3
Fix Version/s: (was: 5.0)
> Make time and byte values more legible
> --------------------------------------
>
> Key: JGRP-2457
> URL: https://issues.redhat.com/browse/JGRP-2457
> Project: JGroups
> Issue Type: Enhancement
> Affects Versions: 5.0.0.Alpha3
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
>
> In an XML configuration, we can already define {{send_buf_size=20M}}, but when printing protocol attribute values, we'll print {{20000000}} instead.
> Change this to print time and bytes values in a more readable format, for all protocol attributes.
> Examples:
> * {{max_credits=3000000}} -> {{max_credits=3m}} // bytes
> * {{time=45000}} -> {{time=45s}} // time
> * {{avg_delivery_time=250.09us}} (note the suffix) // time
> * {{number_of_blockings=234986}} -> {{number_of_blockings=234'986}} // scalar
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month