-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updated hbase:1.4 image causing connection failures #42
Comments
DockerHub is dying with builds backed up for days trying to build images... so I've just pushed the latest 1.4 version myself. Please pull and check against that most recent version (re-running existing build commit is usually sufficient), as I've run a full suite of tests from Advanced Nagios Plugins repo against this HBase 1.4 image. |
I'll be working on re-enabling the extensive automatic test suites against these images later in the month as they were exceeding CI time limits but GitHub Actions is more flexible. |
@HariSekhon Thanks for the reply. I re-ran a Travis job and it doesn't seem to have made a difference. We don't have Travis setup to cache docker images, so it will pull it each time. https://travis-ci.com/github/akka/alpakka/jobs/296475571 I tried locally too, with the same results. The age on the image still shows 6 (now 7) days.
|
Hi @HariSekhon. Were you able to run your testsuites yet? |
@HariSekhon : I think this is the same issue as #43 |
An update to the
HarkiSekhon/hbase:1.4
image broke our Alpakka hbase connector integration test some time after March 8th (last successful hbase integration test build). An earlier cached version of the image (from 2 months ago) seems to work fine.akka/alpakka#2185
Our test clients are failing with several different error messages, but I think the underlying errors are connection timeouts. We update our hosts file to point
hbase
to127.0.0.1
, but this doesn't seem to work locally or on travis, but it did with the old cached version I had.A connection timeout:
Another test complaining about
HADOOP_HOME
. This was never necessary before, so it seems odd that it would be now.The hbase stdout indicates a connection is trying to be made for each of our tests, but does not succeed.
Here's the full log of hbase stdout: https://pastebin.com/x0dy7d8J
The hash of the image we're currently using.
Please let me know if I can provide any additional troubleshooting info or context.
The text was updated successfully, but these errors were encountered: