Github user kwmonroe commented on the issue:
https://github.com/apache/bigtop/pull/153
Thanks for the eyeballs @ktsakalozos and @johnsca! I missed a
mapred.jobhistory binding. You will no longer see any 127.0.x.y bindings.
Also, thanks @johnsca for pointing out the terasort
Github user kwmonroe commented on the issue:
https://github.com/apache/bigtop/pull/153
Charms in ~bigdata-dev namespace have been refreshed and verified that
terasort works on lxd again:
```
results:
meta:
composite:
direction: asc
units: secs
Github user kwmonroe commented on the issue:
https://github.com/apache/bigtop/pull/150
Thanks all. I've refreshed the charm revision numbers to pick up the
recent bind-host options (bigtop-2554) and fix an issue with terasorting on lxd.
---
If your project is set up for it, you can
Github user asfgit closed the pull request at:
https://github.com/apache/bigtop/pull/153
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/bigtop/pull/150
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user ktsakalozos commented on the issue:
https://github.com/apache/bigtop/pull/153
LGTM +1 Tested on lxd and exposed services are indeed listening on the
correct interface.
As you can see we still have some services on 127.0.1.1 but we can handle
any problems we may
Github user johnsca commented on the issue:
https://github.com/apache/bigtop/pull/153
I tested on aws and it works fine, but on lxd I see, like Kostantinos, two
services still listening on 127.0.1.1. Furthermore, terasort fails with the
following the the RM log:
