Return-Path: X-Original-To: apmail-asterixdb-users-archive@minotaur.apache.org Delivered-To: apmail-asterixdb-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 66BA218CD3 for ; Wed, 28 Oct 2015 16:53:17 +0000 (UTC) Received: (qmail 31330 invoked by uid 500); 28 Oct 2015 16:53:17 -0000 Delivered-To: apmail-asterixdb-users-archive@asterixdb.apache.org Received: (qmail 31300 invoked by uid 500); 28 Oct 2015 16:53:17 -0000 Mailing-List: contact users-help@asterixdb.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@asterixdb.incubator.apache.org Delivered-To: mailing list users@asterixdb.incubator.apache.org Received: (qmail 31290 invoked by uid 99); 28 Oct 2015 16:53:17 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2015 16:53:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 989A0180976 for ; Wed, 28 Oct 2015 16:53:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=ics_uci_edu.20150623.gappssmtp.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id LSoWEdGE_N9E for ; Wed, 28 Oct 2015 16:53:05 +0000 (UTC) Received: from mail-oi0-f48.google.com (mail-oi0-f48.google.com [209.85.218.48]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 34B6820924 for ; Wed, 28 Oct 2015 16:53:03 +0000 (UTC) Received: by oies66 with SMTP id s66so8134440oie.1 for ; Wed, 28 Oct 2015 09:53:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ics_uci_edu.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type; bh=26kRLX1w4vXr0orUrvQwCfGAeN3oy+aSYD3SlxJdcws=; b=x03C3qTC9OdZ40lfmyLRp/6Jeakwu6o7jHXKTgNRJROGWuXdKte4ELsq4aY7YXO7hU jFkjCG4Wv0zCyDf3IRRHZ4CvXBBKNdDVOsl1UfrzSbzB2Mj4kOxRWzmQ8CjhSzVbWV0c GbpQGZgHGHy6R+kXYpS7hi4QAgO3tRjuFF7Z63W6N12Zp5Dsl1yZBUBCN3GjuW67sHvT 97y5kfb7/YpsdlJvFET37ISPxcb/Ky8hkJ/KHKI6h6pb/46QVKgtz6ZMYemsE0h3vyNn x6cllIqcJAR9EbukNY+IpnJg5eAIB1Iqc5x19ONd7UQde7xXp1PUCGk564qYfdJePeOI lWoQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-type; bh=26kRLX1w4vXr0orUrvQwCfGAeN3oy+aSYD3SlxJdcws=; b=dPqXJArw+xKB3tOrczF0TdBM6qdxn8ML+mODKwIIKQe4Ta6V/yDul24S8AwsUalBLE Jc9aHOcoGevKegm0CAzyCq4tTXiZV9rBH98Ioiy16UVlMw4yuWq7EhTTMs+A/Rmvec5v F/Bg+miNRk6PKm7ZcT5GlMWLULVWB/1mX6zBLmlLSY+v/9OPue1nglz2fS4009SdeZJ1 XHTWnEn3zrEDLpzACYGp5QUQ1O01KYVNEyAPkmZT5M1qtJCxXi4U0yGAGhZcF7gZCm18 U6fZ3t/PDmI81NNrKAdAdUqAgbe6FtMO+ZWJ2CcMklQLBwEp0dLZrbJ27bk1FHQ9zpfQ cPtA== X-Gm-Message-State: ALoCoQnDNbjFaAgt8V+yGFHZ/3AyfFamnDLItksBrt2enboNDURwd/0X1vtP32RY9MsNqF2ETHWJ X-Received: by 10.202.97.196 with SMTP id v187mr32071528oib.91.1446051182583; Wed, 28 Oct 2015 09:53:02 -0700 (PDT) Received: from mikejcarey.local (ip72-219-184-46.oc.oc.cox.net. [72.219.184.46]) by smtp.gmail.com with ESMTPSA id j10sm19510039obw.0.2015.10.28.09.53.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Oct 2015 09:53:02 -0700 (PDT) Subject: Re: AsterixDB - query status / system status To: users@asterixdb.incubator.apache.org References: <37992.141.20.24.156.1445344846.squirrel@www2.informatik.hu-berlin.de> <55638.91.55.67.181.1445380319.squirrel@www2.informatik.hu-berlin.de> <49153.84.159.203.170.1445860210.squirrel@www2.informatik.hu-berlin.de> <50647.84.159.203.170.1445876099.squirrel@www2.informatik.hu-berlin.de> <39838.79.245.167.242.1446049362.squirrel@www2.informatik.hu-berlin.de> Cc: Pouria Pirzadeh , Yingyi Bu From: Michael Carey Message-ID: <5630FD6C.9010800@ics.uci.edu> Date: Wed, 28 Oct 2015 09:53:00 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------050006000802030201060604" This is a multi-part message in MIME format. --------------050006000802030201060604 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Pouria indeed has a full set of TPC-H queries in AQL.... (Yingyi does too, I believe.) On 10/28/15 9:49 AM, Ian Maxon wrote: > Hi Max, > > Let me respond inline... >> I am currently trying to rewrite some of the TPCH Queries to run them as >> examples on AsterixDB. So far I was able to run some of the queries using >> the web client, but others do not work yet. Unfortunatly sometimes I do >> not get any error messages or results. > I agree, the WebUI leaves something to be desired, especially for > queries that take a long time. > There is one minor amelioration to this however, that I find useful, > the Hyracks admin console. > It's on port 8888 on the CC at /adminconsole . It will show what jobs > are running and which > NCs are still registered with the CC. > > As for rewriting the TPC-H queries, I'm pretty sure we have these (but > the ones in the tests folder aren't, they're toned-down versions). So > maybe you don't have to rewrite anything, hopefully? > @ Pouria, do you happen to have them handy? > > In general though, for more serious use, the HTTP api may be a better > option, as it is more amenable to scripting. > >> As I cannot tell if the queries are still >> running, or if an error occured that is just not displayed, is there a >> possibility to monitor the state of the system/query execution? > The adminconsole will show if there's a job still running, but not > exceptional states that cause the job to hang. > The exceptions should be in the CC log always. Where that is depends > on your managix configuration (but it's always called cc.log). > > >From time to time the system even crashes and I cannot even shut it down >> using managix stop. > Yes, unfortunately 'managix stop' just goes through the list of NC's > and requests 'kill' on the process, not 'kill' and then 'kill -9'. In > the cases where an NC fails to exit politely, it has to be done by > hand for managix. > > By the way, what environment are you running everything on? Is it a cluster? > > Thanks, > -Ian > > On Wed, Oct 28, 2015 at 9:22 AM, wrote: >> Hello, >> >> by now I was able to successfully install AsterixDB from the latest master >> branch which also made it possible for me to load external data files into >> the system. Thanks a lot for the help! >> >> I am currently trying to rewrite some of the TPCH Queries to run them as >> examples on AsterixDB. So far I was able to run some of the queries using >> the web client, but others do not work yet. Unfortunatly sometimes I do >> not get any error messages or results. On execution the output area of the >> webclient turns blank as it usually does, but after some time I should get >> the results shown (or an error). As I cannot tell if the queries are still >> running, or if an error occured that is just not displayed, is there a >> possibility to monitor the state of the system/query execution? >> >> From time to time the system even crashes and I cannot even shut it down >> using managix stop. >> >> Regards, Max >> >> >>> Your assumption is correct, for the latest AsterixDB master we usually >>> depend on the development version of Hyracks >>> (https://github.com/apache/incubator-asterixdb-hyracks/). 'mvn install >>> -DskipTests' with Hyracks should do the trick. >>> >>> Thanks, >>> -Ian >>> --------------050006000802030201060604 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit Pouria indeed has a full set of TPC-H queries in AQL....
(Yingyi does too, I believe.)

On 10/28/15 9:49 AM, Ian Maxon wrote:
Hi Max,

Let me respond inline...
I am currently trying to rewrite some of the TPCH Queries to run them as
examples on AsterixDB. So far I was able to run some of the queries using
the web client, but others do not work yet. Unfortunatly sometimes I do
not get any error messages or results.
I agree, the WebUI leaves something to be desired, especially for
queries that take a long time.
There is one minor amelioration to this however, that I find useful,
the Hyracks admin console.
It's on port 8888 on the CC at /adminconsole . It will show what jobs
are running and which
NCs are still registered with the CC.

As for rewriting the TPC-H queries, I'm pretty sure we have these (but
the ones in the tests folder aren't, they're toned-down versions). So
maybe you don't have to rewrite anything, hopefully?
@ Pouria, do you happen to have them handy?

In general though, for more serious use, the HTTP api may be a better
option, as it is more amenable to scripting.

As I cannot tell if the queries are still
running, or if an error occured that is just not displayed, is there a
possibility to monitor the state of the system/query execution?
The adminconsole will show if there's a job still running, but not
exceptional states that cause the job to hang.
The exceptions should be in the CC log always. Where that is depends
on your managix configuration (but it's always called cc.log).

>From time to time the system even crashes and I cannot even shut it down
using managix stop.
Yes, unfortunately 'managix stop' just goes through the list of NC's
and requests 'kill' on the process, not 'kill' and then 'kill -9'. In
the cases where an NC fails to exit politely, it has to be done by
hand for managix.

By the way, what environment are you running everything on? Is it a cluster?

Thanks,
-Ian

On Wed, Oct 28, 2015 at 9:22 AM,  <schultze@informatik.hu-berlin.de> wrote:
Hello,

by now I was able to successfully install AsterixDB from the latest master
branch which also made it possible for me to load external data files into
the system. Thanks a lot for the help!

I am currently trying to rewrite some of the TPCH Queries to run them as
examples on AsterixDB. So far I was able to run some of the queries using
the web client, but others do not work yet. Unfortunatly sometimes I do
not get any error messages or results. On execution the output area of the
webclient turns blank as it usually does, but after some time I should get
the results shown (or an error). As I cannot tell if the queries are still
running, or if an error occured that is just not displayed, is there a
possibility to monitor the state of the system/query execution?

>From time to time the system even crashes and I cannot even shut it down
using managix stop.

Regards, Max


Your assumption is correct, for the latest AsterixDB master we usually
depend on the development version of Hyracks
(https://github.com/apache/incubator-asterixdb-hyracks/). 'mvn install
-DskipTests' with Hyracks should do the trick.

Thanks,
-Ian


      

--------------050006000802030201060604--