From dev-return-827-archive-asf-public=cust-asf.ponee.io@fluo.apache.org Fri Mar 16 13:35:33 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 432DF180608 for ; Fri, 16 Mar 2018 13:35:33 +0100 (CET) Received: (qmail 13609 invoked by uid 500); 16 Mar 2018 12:35:32 -0000 Mailing-List: contact dev-help@fluo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fluo.apache.org Delivered-To: mailing list dev@fluo.apache.org Received: (qmail 13588 invoked by uid 99); 16 Mar 2018 12:35:31 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2018 12:35:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 3F4461A06F9 for ; Fri, 16 Mar 2018 12:35:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.02 X-Spam-Level: X-Spam-Status: No, score=-0.02 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=deenlo-com.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 4rtwNgpeeWMX for ; Fri, 16 Mar 2018 12:35:29 +0000 (UTC) Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com [209.85.220.179]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 681705F4DC for ; Fri, 16 Mar 2018 12:35:28 +0000 (UTC) Received: by mail-qk0-f179.google.com with SMTP id o184so10754862qkd.13 for ; Fri, 16 Mar 2018 05:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=deenlo-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Q9R5OtECFI+KFbYAAnrM6+/aK4DoIW+hP4anr5SzRQw=; b=oP2P/ZWjyavVnawkpjeBz38L5PFz24UigerEcQEvulO9ys6d3lKn3dpwJVg8SlCPCV 1GddjK/XLyZd45qKfuGQ715n5AcOFT/OUia4/ydqRR2zfslzT6o1jvnMypLIJf1Lorl6 8Zt+hJ5w2bnIKUtitYHnN6ngSLwHr14kD/HoHAfC47sAKn+MlX4dxgYPU28uZKr3h/1j b8kfmF18pJN7sgeQg74vifRvyFEATGOwFXGiIVLK9BUiJ5IW9PfI4ZHIRvUr7bkIAJfu xw2oaJqOJxi1C7K+RkXJsekYtv1732CZx6b8H6FC5WebocC+dotKkKd++m57vy0I85NL pz5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Q9R5OtECFI+KFbYAAnrM6+/aK4DoIW+hP4anr5SzRQw=; b=Iu8dBD0Zp3HPw655uFXWDU9tZ+e8eRyIAgUZFoP1njeOnr8eg6+FrrJvmh2m1ipQ4c gdaIyCbZ6mDE8xWxtj4Zbtngyd21xF/AeRxf47kdyUGp4FluP3Ti64B6vbm9AQQT+BzP WNoCrt+sZ3TUZsvBeqCyLYbOEwcOavhIxMoTOvYcMiqoguHy9J8Z9eWUmHqXI+LUg/n0 l3RPzy2RDTquxTkTgupF6iWRJBJvkZHn93JKXt08eN5MtYX8zcJH3yM/AyNNLUDNzdqB 0QG5ygjXEfB7m6yoeHRBfV+UveT3Drs/nqZzwaG7quLg5/GKbWJq2uuFnSm4J/3JZz8g EhoQ== X-Gm-Message-State: AElRT7EvBj5INeBvsh0E4xepC721boNC9STtkOod4Fo0ZL1cWpAWqeVe mfKut+wml7D1dmI07FRq8eU0Sa3tJmT2vsgUur9ykg== X-Google-Smtp-Source: AG47ELu6cGXNvNlSnAAE086p44A70LmwaFOzc7vQwXyL7CldV7WDmvktCKe+QRQjO5wjpVvaiieOrLP+9IaSIAxP5k8= X-Received: by 10.55.21.40 with SMTP id f40mr2226003qkh.287.1521203721079; Fri, 16 Mar 2018 05:35:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.244.206 with HTTP; Fri, 16 Mar 2018 05:35:20 -0700 (PDT) In-Reply-To: References: From: Keith Turner Date: Fri, 16 Mar 2018 08:35:20 -0400 Message-ID: Subject: Re: Create apache/fluo repo on DockerHub To: fluo-dev Content-Type: text/plain; charset="UTF-8" On Thu, Mar 15, 2018 at 2:46 PM, Alan Camillo 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 : > >> On Thu, Mar 15, 2018 at 2:29 PM, Alan Camillo >> 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.( >> StaticHostProvider.java:62) >> > at org.apache.zookeeper.ZooKeeper.(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.(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.( >> StaticHostProvider.java:88) >> > at org.apache.zookeeper.ZooKeeper.(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.(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 : >> > >> >> 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 >> >> 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 < >> >> kennethpmcfarland@gmail.com >> >> > >: >> >> > >> >> > > +1 >> >> > > >> >> > > On Feb 28, 2018 9:42 AM, "Christopher" wrote: >> >> > > >> >> > > +1 >> >> > > >> >> > > On Wed, Feb 28, 2018 at 11:54 AM Keith Turner >> >> wrote: >> >> > > >> >> > > > I am in favor of creating this. >> >> > > > >> >> > > > On Wed, Feb 28, 2018 at 11:15 AM, Mike Walch >> >> > 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. >> >> > > > >> >> > > >> >> > >> >> >>