giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavan Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GIRAPH-821) proper handling of NegativeArraySizeException for all ByteArray backed messagestores
Date Wed, 08 Jan 2014 22:22:50 GMT

     [ https://issues.apache.org/jira/browse/GIRAPH-821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavan Kumar updated GIRAPH-821:
-------------------------------

    Attachment: GIRAPH-821-v1.patch

mentioned the option in error message.

>  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-v1.patch, 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)

Mime
View raw message