flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10412) toString field in AbstractID should be transient to avoid been serialized
Date Mon, 08 Oct 2018 08:08:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16641490#comment-16641490
] 

ASF GitHub Bot commented on FLINK-10412:
----------------------------------------

yanghua commented on issue #6755: [FLINK-10412] toString field in AbstractID should be transient
to avoid been serialized
URL: https://github.com/apache/flink/pull/6755#issuecomment-427751092
 
 
   @tillrohrmann I have tried to do it the way you said it, but because the fully qualified
names of the two classes are different, an exception is thrown when the type conversion is
done.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> toString field in AbstractID should be transient to avoid been serialized
> -------------------------------------------------------------------------
>
>                 Key: FLINK-10412
>                 URL: https://issues.apache.org/jira/browse/FLINK-10412
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Coordination
>    Affects Versions: 1.7.0
>            Reporter: Zhu Zhu
>            Assignee: vinoyang
>            Priority: Major
>              Labels: deploy,deployment, pull-request-available, serialization
>
> The toString field in AbstractID will be serialized currently, which makes RPC messages
body like InputChannelDeploymentDescriptor and PartitionInfo larger (50%+).
> It adds more pressure to JM memory especially in large scale job scheduling (10000x10000
ALL-to-ALL connection).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message