[
https://issues.apache.org/jira/browse/GIRAPH-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavan Kumar updated GIRAPH-821:
-------------------------------
Attachment: Testing.patch
These changes can be applied on top of the giraph-821 patch, to be able to
verify that it works. [caution: this patch does not conform to check style of
giraph]
this can be used to verify the patch works. indeed that is how I tested it.
mvn -Dcheckstyle.skip=true -Dtest=TestLongByteArrayMessageVerboseException test
> proper handling of NegativeArraySizeException for all ByteArray backed
> messagestores
> -------------------------------------------------------------------------------------
>
> Key: GIRAPH-821
> URL: https://issues.apache.org/jira/browse/GIRAPH-821
> Project: Giraph
> Issue Type: Improvement
> Reporter: Pavan Kumar
> Assignee: Pavan Kumar
> Priority: Minor
> Labels: giraph
> Attachments: GIRAPH-821.patch, Testing.patch
>
>
> For byte array backed message stores (i.e. LongByteArrayMessageStore,
> ByteArrayMessagesPerVertexMessageStore, and IntByteArrayMessageStore)
> currently, when the byte[] of underlying ExtendedDataOuput runs out of space
> (i.e. UnsafeByteArrayOutputStream) we see
> java.lang.NegativeArraySizeException in the SendWorkerMessagesRequest. We
> want to catch the exception dump the known vertex information and explain the
> issue (the amount of bytes sent to this vertex exceeded the max capacity
> of this ExtendedDataOutput). In this diff all ByteArray backed
> messagestores have been modified to behave as explained.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
