tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Poorna Chandra <poo...@apache.org>
Subject Re: Tephra unreliable in CI environments
Date Wed, 28 Sep 2016 02:04:37 GMT
Hi Francis,

Tephra startup script redirects all logs to a file by default. To help
debug such issues, you could update the Tephra startup script [1] to log
everything to stdout instead of a file when running inside docker. We are
also planning on adding a --foreground option to Tephra startup script, in
which case the logs will be written to stdout directly. This will help in
debugging in future.


[1] - https://github.com/apache/incubator-tephra/blob/master/bin/tephra#L175

On Tue, Sep 27, 2016 at 12:59 AM, F21 <f21.groups@gmail.com> wrote:

> I was able to get it to run reliably with Phoenix 4.8.1-rc0. Another part
> of the equation was forcing travis to use their Ubuntu 14.04 environment
> rather than the default 12.04 environment. I am assuming 12.04 had an older
> kernel which prevent docker images from working correctly.
> On 27/09/2016 10:15 AM, F21 wrote:
>> Hi all,
>> I have created a docker image containing HBase 1.2.3 and Phoenix 4.8.0.
>> See: https://github.com/Boostport/hbase-phoenix-all-in-one
>> When running tests against the image on my machine, tephra works
>> perfectly.
>> However, tephra seems to be unreliable in CI environments. It seems that
>> the tx service is not discovered:
>> RuntimeException: java.lang.Exception: Thrift error for
>> org.apache.tephra.distributed.TransactionServiceClient$2@3e9e291e:
>> Unable to discover tx service. -> Exception: Thrift error for
>> org.apache.tephra.distributed.TransactionServiceClient$2@3e9e291e:
>> Unable to discover tx service. -> TException: Unable to discover tx service.
>> Here's a build on wercker which shows tephra failing:
>> https://app.wercker.com/boostport/avatica/runs/build/57e9b5d
>> 170a35501008402b4?step=57e9b5f72c15ad000127a534
>> I also tried travis, but the same issue occurs:
>> https://travis-ci.org/Boostport/avatica/builds/162952367
>> Since I am unable to ssh into those docker container on wercker or
>> travis, it is hard to debug what's causing tephra to fail. I am hoping that
>> the issue is related to TEPHRA-179 (and a few other JIRAs related to it)
>> which I reported a few weeks ago and has since been fixed.
>> Has anyone else ran into similar problems? I would love to hear your
>> thoughts.
>> Cheers,
>> Francis

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message