accumulo-notifications mailing list archives

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


Josh Elser commented on ACCUMULO-4051:

bq. I'm not familiar with how the projects are entwined

Accumulo is a consumer of Thrift. Accumulo uses Thrift for *all* of its RPC. As a distributed
system, this is a lot :)

bq. it seems like Accumulo should track Thrift if possible

We do, as time/effort exists to perform the necessary testing and upgrading. Unless there
is a critical bug that gets fixed that is affecting us, we tend to miss Thrift point releases
because it's not worth the pain to upgrade. This could be lessened by better stability from
Thrift itself (e.g. API guarantees, tests in thrift to catch perf regressions early, etc).

bq.  If there's some sort of basic documentation for running the unit tests, I could take
a shot at getting a branch working with the latest Thrift.

The normal Maven lifecycle phases are your best entry point for automated testing ({{mvn package}}
for unit tests and {{mvn verify}} for integration tests). However, this does not cover performance
or multiple node tests which are the time consuming ones to vet/verify.

We have distributed tests in the form of [Continuous Ingest|]
and [Randomwalk|]
which are great tests that run across many nodes, but they are a manual effort to set up.

Hopefully, this isn't discouraging. Any way you are able to help this effort would be appreciated.
Feel free to ask more specific questions on our [mailing list|].

> Investigate updating Thrift
> ---------------------------
>                 Key: ACCUMULO-4051
>                 URL:
>             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

View raw message