zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tamas Penzes (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-102) Need to replace Jute with supported code
Date Wed, 09 Oct 2019 12:13:00 GMT

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

Tamas Penzes commented on ZOOKEEPER-102:
----------------------------------------

[~maoling], [~tison] have you thought about upgrade from ZK 3.5 to 4 with rolling restart?

If ZK 4 won't be compatible with ZK 3 at all, how do we have a migration path for existing
users.

If we kept Jute based communication for a while, but start having another one (e.g. protobuf)
on an another port, we could do a rolling upgrade. Of course we would need config parameters
about which one is enabled to be able to switch off the not needed ports (e.g. jute based
one after the migration).

Just my 2 cents.

> 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)

Mime
View raw message