accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4051) Investigate updating Thrift
Date Mon, 30 Nov 2015 16:22:11 GMT

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

Josh Elser commented on ACCUMULO-4051:
--------------------------------------

[~tlippy01], the problem for us is that it typically requires testing with a very close eye
after upgrading Thrift. Historically, we've been bitten many, many times after upgrading the
version of Thrift with performance regressions and more.

As such, the worry from Accumulo's end is "will we have more issues?", but this isn't a blocker
from doing it. We just need someone who can sit down, upgrade to 0.9.3, and run some of our
tests over multiple nodes to check things out.

In other words, I don't think we need multiple layers of planning yet; we just need someone
to investigate.

> Investigate updating Thrift
> ---------------------------
>
>                 Key: ACCUMULO-4051
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4051
>             Project: Accumulo
>          Issue Type: Task
>          Components: rpc
>            Reporter: Josh Elser
>             Fix For: 1.8.0
>
>
> 1.8.0 is still on Thrift 0.9.1. Thrift has since released 0.9.2 and 0.9.3. We should
consider what has been fixed in the Java libs since 0.9.1 and try to identify whether or not
it would be worth to try to update.
> If deciding to update, then we need to do some testing to make sure Thrift didn't accidentally
break/degrade anything.
> It behooves us to keep close to the edge of Thrift to maintain compatibility, so hopefully
we can look at this before 1.8.0 happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message