Return-Path: X-Original-To: apmail-asterixdb-dev-archive@minotaur.apache.org Delivered-To: apmail-asterixdb-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B568D188D3 for ; Mon, 9 Nov 2015 19:44:21 +0000 (UTC) Received: (qmail 53947 invoked by uid 500); 9 Nov 2015 19:44:21 -0000 Delivered-To: apmail-asterixdb-dev-archive@asterixdb.apache.org Received: (qmail 53892 invoked by uid 500); 9 Nov 2015 19:44:21 -0000 Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@asterixdb.incubator.apache.org Delivered-To: mailing list dev@asterixdb.incubator.apache.org Received: (qmail 53878 invoked by uid 99); 9 Nov 2015 19:44:21 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2015 19:44:21 +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 0525A1A0CD6 for ; Mon, 9 Nov 2015 19:44:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.97 X-Spam-Level: X-Spam-Status: No, score=0.97 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 3uqXnzVpa9Q8 for ; Mon, 9 Nov 2015 19:44:20 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 1115C21270 for ; Mon, 9 Nov 2015 19:44:20 +0000 (UTC) Received: (qmail 53873 invoked by uid 99); 9 Nov 2015 19:44:19 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Nov 2015 19:44:19 +0000 Received: from [10.17.1.105] (unknown [206.169.106.2]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id BDEDB1A012E for ; Mon, 9 Nov 2015 19:44:19 +0000 (UTC) From: "Till Westmann" To: dev@asterixdb.incubator.apache.org Subject: Re: debugging RecoveryIT Date: Mon, 09 Nov 2015 11:44:19 -0800 Message-ID: <73FEA552-74A4-4563-9B90-5893CD2FF8CE@apache.org> In-Reply-To: References: <42F9DBCF-4AED-4E67-8EBE-07805A9B4A5B@gmail.com> <66900AE4-FEA6-4D7C-88F8-92DACE7272BF@gmail.com> <5B3A5793-3EF8-4431-95D8-A2670734C8D6@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailer: MailMate (1.9.2r5141) Thanks. I’ve added both original approaches to the Wiki [1]. Please add other tips/hints/practices that could be useful to debug AsterixDB to that page. I think that it should be ‘suspend=y’. Does 'suspend=1' work as well? Cheers, Till [1] https://cwiki.apache.org/confluence/display/ASTERIXDB/Debugging On 9 Nov 2015, at 7:47, Ian Maxon wrote: > Another tweak would be to specify 'suspend=1' along with the debug > port option in asterix-configuration.xml. That'd stop the CC/NC from > starting until the debugger's actually attached. > > On Fri, Nov 6, 2015 at 6:16 PM, Till Westmann > wrote: >> Tried that as well and it worked, but it feels sub-optimal :) >> >> Murtadha’s way also works nicely (and doesn’t require short >> reaction times!) >> if you don’t want to be strictly in the RecoveryIT context. >> >> Cheers, >> Till >> >> >> On 6 Nov 2015, at 17:04, Young-Seok Kim wrote: >> >>> I was doing what Ildar did and I did attaching quickly. :( >>> >>> On Fri, Nov 6, 2015 at 4:34 PM, Till Westmann >>> wrote: >>> >>>> Thanks for both replies! >>>> >>>> @Ildar: When you added the JVM parameters for the CC or NC, how did >>>> you >>>> go >>>> about attaching at the “right” point in time? Did you stop the >>>> JVM >>>> waiting >>>> for the connection or were you “attaching quickly”? >>>> >>>> Thanks again, >>>> Till >>>> >>>> >>>> On 5 Nov 2015, at 22:47, Murtadha Hubail wrote: >>>> >>>> I think the easiest way without having to attach a remote debugger >>>> is to >>>>> >>>>> execute their queries manually in the web interface after running >>>>> AsterixHyracksIntegrationUtil in debugging mode. When it is time >>>>> to >>>>> execute >>>>> kill_cc_nc.sh, just kill -9 the AsterixHyrackIntegrationUtil >>>>> process. >>>>> Then >>>>> run AsterixHyrackIntegrationUtil again and it will perform the >>>>> recovery. >>>>> >>>>> -Murtadha >>>>> >>>>> On Nov 5, 2015, at 10:14 PM, Ildar Absalyamov >>>>> >>>>>> >>>>>> wrote: >>>>>> >>>>>> Till, >>>>>> >>>>>> The only way I found to debug it sometime ago when I needed was >>>>>> to add >>>>>> remote debugger into CC/NC JVM properties of >>>>>> asterix-configuration.xml >>>>>> (asterix-installer/src/main/resources/conf), which is used to >>>>>> setup >>>>>> mini >>>>>> cluster to tests. >>>>>> >>>>>> On Nov 6, 2015, at 11:07, Till Westmann wrote: >>>>>>> >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I’m wondering how people go about running the code that is >>>>>>> executed by >>>>>>> one of the RecoveryIT in the debugger. >>>>>>> I imagine that there are number of ways to do that. >>>>>>> If you have done this at some point, could you describe how you >>>>>>> did >>>>>>> that? >>>>>>> >>>>>>> Thanks, >>>>>>> Till >>>>>>> >>>>>> >>>>>> Best regards, >>>>>> Ildar >>>>>> >>>>>> >>