[
https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950880#comment-16950880
]
maoling commented on ZOOKEEPER-102:
-----------------------------------
* If we move to other serialization library and only gain about 10% performance
booster, Is it all completely unnecessary to replace Jute? Serialization may be
not a bottle-neck for the system?
* Starting another port for rolling upgrade will cause some unexpected issues,
especially when leader changes, node reconfigs etc. If users have a proxy layer
in front of zk ensemble, that will make upgrade easily.
* IMHO, in the future(4.0.0), we will emphasize more on restful/http api than
C client to support multi-languages.
> Need to replace Jute with supported code
> ----------------------------------------
>
> Key: ZOOKEEPER-102
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-102
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Benjamin Reed
> Priority: Major
> Fix For: 4.0.0
>
>
> ZooKeeper currently uses Jute to serialize objects to put on the wire and on
> disk. We pulled Jute out of Hadoop and added a C binding. Both versions of
> Jute have evolved (although Hadoop still doesn't have a C binding). It would
> be nice to use a more standard serialization library. Some options include
> Thrift or Google's protocol buffers.
> Our main requirements would be Java and C bindings and good performance. (For
> example, serializing to XML would give us incredibly bad performance and
> would not be acceptible!)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
