Closed
Bug 1276315
Opened 10 years ago
Closed 10 years ago
crash aggregates for 25/5 and 26/5 not available on re:dash
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mdoglio, Assigned: mdoglio)
Details
Attachments
(1 file)
|
49.80 KB,
text/plain
|
Details |
The crash aggregates job ran successfully and the data is in s3, but it's not on re:dash. Running manually the parquet2hive script made the data appear on re:dash as well but it's still not clear why it wasn't there in the first place
| Assignee | ||
Comment 1•10 years ago
|
||
Here is the output I got running manually
> /usr/local/bin/parquet2hive s3://telemetry-parquet/crash_aggregates | bash
Comment 2•10 years ago
|
||
Looking at the cron mail, I am seeing that the current failure mode began Thu, 26 May 2016 00:03:02 GMT and all parquet2hive calls on cron have failed since. The errors look like:
bash: line 1: Failure: command not found
This is most likely due to https://github.com/vitillo/parquet2hive/blob/master/parquet2hive/parquet2hive#L173, indicating some kind of failure. However, the error is not listed in the cron output, so I've instrumented the cron jobs to also write the bash output to files to see what the exception is. This should hopefully also indicate why it doesn't happen when run manually.
| Assignee | ||
Comment 3•10 years ago
|
||
I'll close this bug because the parquet2hive cron has worked correctly since I ran the command manually.
Please reopen it if the problem shows up again.
Assignee: nobody → mdoglio
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•