Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id ADA541897A for ; Tue, 26 May 2015 18:57:17 +0000 (UTC) Received: (qmail 244 invoked by uid 500); 26 May 2015 18:57:17 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 216 invoked by uid 500); 26 May 2015 18:57:17 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 206 invoked by uid 99); 26 May 2015 18:57:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 May 2015 18:57:17 +0000 Date: Tue, 26 May 2015 18:57:17 +0000 (UTC) From: "Chris Westin (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-2248) Create script that collects information on drill configuration and logs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Westin updated DRILL-2248: -------------------------------- Fix Version/s: (was: 1.1.0) 1.2.0 > Create script that collects information on drill configuration and logs > ----------------------------------------------------------------------- > > Key: DRILL-2248 > URL: https://issues.apache.org/jira/browse/DRILL-2248 > Project: Apache Drill > Issue Type: New Feature > Components: Tools, Build & Test > Reporter: Victoria Markman > Assignee: Sudheesh Katkam > Fix For: 1.2.0 > > > Sometimes drill fails in ways that are very difficult to recreate in-house. > We should create a script that collects all the information below and compresses it all in one tarball that can be shipped to us for analysis: > * Cluster physical characteristics: number of nodes, memory, disks, cpus ... > * MapR versions of all the components running on the cluster > * Drill specific information: > * rpm version > * drill configuration > * log files > * query profiles > * output of sys.options > Btw, if user set session specific option, will we be able to see what was set when query was running ? Is it recorded anywhere ? > Anything else we think is important. -- This message was sent by Atlassian JIRA (v6.3.4#6332)