From issues-return-1531-archive-asf-public=cust-asf.ponee.io@zookeeper.apache.org Wed Oct 9 12:13:05 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id ABCD2180658 for ; Wed, 9 Oct 2019 14:13:04 +0200 (CEST) Received: (qmail 64710 invoked by uid 500); 9 Oct 2019 12:13:04 -0000 Mailing-List: contact issues-help@zookeeper.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zookeeper.apache.org Delivered-To: mailing list issues@zookeeper.apache.org Received: (qmail 64697 invoked by uid 99); 9 Oct 2019 12:13:04 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Oct 2019 12:13:04 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 62549E316E for ; Wed, 9 Oct 2019 12:13:03 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id B28B2780AD9 for ; Wed, 9 Oct 2019 12:13:00 +0000 (UTC) Date: Wed, 9 Oct 2019 12:13:00 +0000 (UTC) From: "Tamas Penzes (Jira)" To: issues@zookeeper.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ZOOKEEPER-102) Need to replace Jute with supported code MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ZOOKEEPER-102?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1= 6947601#comment-16947601 ]=20 Tamas Penzes commented on ZOOKEEPER-102: ---------------------------------------- [~maoling], [~tison]=C2=A0have you thought about upgrade from ZK 3.5 to 4 w= ith rolling restart? If ZK 4 won't be compatible with ZK 3 at all, how do we have a migration pa= th for existing users. If we kept Jute based communication for a while, but start having another o= ne (e.g. protobuf) on an another port, we could do a rolling upgrade. Of co= urse 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 in= clude 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 a= nd would not be acceptible!) -- This message was sent by Atlassian Jira (v8.3.4#803005)