You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Chris Westin (JIRA)" <ji...@apache.org> on 2015/04/22 19:00:59 UTC
[jira] [Updated] (DRILL-2248) Create script that collects
information on drill configuration and logs
[ https://issues.apache.org/jira/browse/DRILL-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Westin updated DRILL-2248:
--------------------------------
Assignee: Sudheesh Katkam
> 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.1.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)