On Thu, Mar 15, 2018 at 2:46 PM, Alan Camillo <a...@blueshift.com.br> wrote: > Ok! I imagine something like that. But tried anyway. > Its logic that I have to already have a cluster with HDFS, ZK and ACCUMULO > running and than point my fluo-app.properties to it. > > I think we could make this explicit on documentation. Just in case!
I created a PR to update the docs. > > Alan Camillo > *BlueShift *I IT Director > Cel.: +55 11 98283-6358 > Tel.: +55 11 4605-5082 > > 2018-03-15 15:35 GMT-03:00 Keith Turner <ke...@deenlo.com>: > >> On Thu, Mar 15, 2018 at 2:29 PM, Alan Camillo <a...@blueshift.com.br> >> wrote: >> > Nice Mike! >> > >> > But I have an user question, does this should execute well*:* >> > >> >> docker run --network="host" -v /home/docker-user/share/:/opt/myapp -e >> > HADOOP_USER_NAME=user01 apache/fluo init -a myapp -f -p >> > /opt/myapp/fluo-app.properties -o fluo.connection.zookeepers=zkhost/fluo >> >> Need to replace zkhost with hostname(s) for zookeepers. >> >> > >> > >> > *But I received this error. Should I do something different that manual?* >> > >> > 2018-03-15 18:09:12,706 [client.StaticHostProvider] ERROR: Unable to >> > connect to server: zkhost:2181 >> > java.net.UnknownHostException: zkhost: Name or service not known >> > at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) >> > at java.net.InetAddress$2.lookupAllHostAddr(InetAddress. >> java:928) >> > at >> > java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323) >> > at java.net.InetAddress.getAllByName0(InetAddress.java:1276) >> > at java.net.InetAddress.getAllByName(InetAddress.java:1192) >> > at java.net.InetAddress.getAllByName(InetAddress.java:1126) >> > at >> > org.apache.zookeeper.client.StaticHostProvider.<init>( >> StaticHostProvider.java:62) >> > at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:449) >> > at >> > org.apache.curator.utils.DefaultZookeeperFactory.newZooKeeper( >> DefaultZookeeperFactory.java:29) >> > at >> > org.apache.curator.framework.imps.CuratorFrameworkImpl$2.newZooKeeper( >> CuratorFrameworkImpl.java:146) >> > at >> > org.apache.curator.HandleHolder$1.getZooKeeper(HandleHolder.java:94) >> > at >> > org.apache.curator.HandleHolder.getZooKeeper(HandleHolder.java:55) >> > at >> > org.apache.curator.ConnectionState.reset(ConnectionState.java:218) >> > at >> > org.apache.curator.ConnectionState.start(ConnectionState.java:102) >> > at >> > org.apache.curator.CuratorZookeeperClient.start( >> CuratorZookeeperClient.java:189) >> > at >> > org.apache.curator.framework.imps.CuratorFrameworkImpl. >> start(CuratorFrameworkImpl.java:248) >> > at >> > org.apache.fluo.core.client.FluoAdminImpl.<init>(FluoAdminImpl.java:84) >> > at org.apache.fluo.command.FluoInit.main(FluoInit.java:135) >> > 2018-03-15 18:09:12,708 [imps.CuratorFrameworkImpl] ERROR: Background >> > exception was not retry-able or retry gave up >> > java.lang.IllegalArgumentException: A HostProvider may not be empty! >> > at >> > org.apache.zookeeper.client.StaticHostProvider.<init>( >> StaticHostProvider.java:88) >> > at org.apache.zookeeper.ZooKeeper.<init>(ZooKeeper.java:449) >> > at >> > org.apache.curator.utils.DefaultZookeeperFactory.newZooKeeper( >> DefaultZookeeperFactory.java:29) >> > at >> > org.apache.curator.framework.imps.CuratorFrameworkImpl$2.newZooKeeper( >> CuratorFrameworkImpl.java:146) >> > at >> > org.apache.curator.HandleHolder$1.getZooKeeper(HandleHolder.java:94) >> > at >> > org.apache.curator.HandleHolder.getZooKeeper(HandleHolder.java:55) >> > at >> > org.apache.curator.ConnectionState.reset(ConnectionState.java:218) >> > at >> > org.apache.curator.ConnectionState.start(ConnectionState.java:102) >> > at >> > org.apache.curator.CuratorZookeeperClient.start( >> CuratorZookeeperClient.java:189) >> > at >> > org.apache.curator.framework.imps.CuratorFrameworkImpl. >> start(CuratorFrameworkImpl.java:248) >> > at >> > org.apache.fluo.core.client.FluoAdminImpl.<init>(FluoAdminImpl.java:84) >> > at org.apache.fluo.command.FluoInit.main(FluoInit.java:135) >> > >> > Alan Camillo >> > *BlueShift *I IT Director >> > Cel.: +55 11 98283-6358 >> > Tel.: +55 11 4605-5082 >> > >> > 2018-03-15 14:46 GMT-03:00 Mike Walch <mwa...@apache.org>: >> > >> >> The apache/fluo docker image is now available on DockerHub: >> >> >> >> https://hub.docker.com/r/apache/fluo/ >> >> >> >> Below are instructions for using the image: >> >> >> >> https://fluo.apache.org/docs/fluo/1.2/administration/run-fluo-in-docker >> >> >> >> >> >> On Wed, Feb 28, 2018 at 1:06 PM, Alan Camillo <a...@blueshift.com.br> >> >> wrote: >> >> >> >> > Great! >> >> > >> >> > Alan Camillo >> >> > *BlueShift *I IT Director >> >> > Cel.: +55 11 98283-6358 >> >> > Tel.: +55 11 4605-5082 >> >> > >> >> > 2018-02-28 14:56 GMT-03:00 kenneth mcfarland < >> >> kennethpmcfarl...@gmail.com >> >> > >: >> >> > >> >> > > +1 >> >> > > >> >> > > On Feb 28, 2018 9:42 AM, "Christopher" <ctubb...@apache.org> wrote: >> >> > > >> >> > > +1 >> >> > > >> >> > > On Wed, Feb 28, 2018 at 11:54 AM Keith Turner <ke...@deenlo.com> >> >> wrote: >> >> > > >> >> > > > I am in favor of creating this. >> >> > > > >> >> > > > On Wed, Feb 28, 2018 at 11:15 AM, Mike Walch <mwa...@apache.org> >> >> > wrote: >> >> > > > > Starting with Fluo 1.2.0, we tell users that they can obtain an >> >> > > > apache/fluo >> >> > > > > image from DockerHub: >> >> > > > > >> >> > > > > https://fluo.apache.org/docs/fluo/1.2/administration/run- >> >> > > fluo-in-docker >> >> > > > > >> >> > > > > I would like to put in a ticket with INFRA to create this repo. >> If >> >> no >> >> > > one >> >> > > > > has objections, I will do this tomorrow. >> >> > > > >> >> > > >> >> > >> >> >>
