Details
-
New Feature
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
DRILL-2601 Print SQL query text along with query id in drillbit.log
- Closed