[
https://issues.apache.org/jira/browse/DRILL-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310569#comment-15310569
]
John Omernik commented on DRILL-2593:
-------------------------------------
Big +1 one from me, here is my user list post on the subject. This should be
easily reproducible, and for end users/admins it could be quite the issue
trying the track down the troublesome profile. We should really address this
for user exp reasons.
John
Post from User list:
It is absolutely a bad profile, however, it was not a empty file profile,
instead, it was a profile where the write didn't complete (likely due to my bad
cluster state post).
I was able to reproduce it synthetically like this, say you had a profile that
ended similar to this:
..."endpoint":{"address":"zeta01.mydomain.net","userPort":20001,"controlPort":20002,"dataPort":20003},"lastUpdate":1464730828126,"lastProgress":1464730828126}]}],"user":"adm"}
(The ... represents the part I removed for brevity in this email, the rest of
the profile is below)
We can reproduce the UI profiles issue by removing ,"user":"adm"}
so it ends like this:
..."endpoint":{"address":"zeta01.mydomain.net","userPort":20001,"controlPort":20002,"dataPort":20003},"lastUpdate":1464730828126,"lastProgress":1464730828126}]}]
Let me know if you know of a JIRA, otherwise I'll open one, this is a pain for
users, because you have to go through an validate the json on every profile to
find the one that is breaking your UI.
John
Full "Working" Profile:
{"id":{"part1":2932401029014293687,"part2":6412631480783062510},"type":1,"start":1464730828036,"end":1464730828131,"query":"alter
session set `store.parquet.enable_dictionary_encoding` =
true","foreman":{"address":"zeta01.mydomain.net","userPort":20001,"controlPort":20002,"dataPort":20003},"state":2,"totalFragments":1,"finishedFragments":0,"fragmentProfile":[{"majorFragmentId":0,"minorFragmentProfile":[{"state":3,"minorFragmentId":0,"operatorProfile":[{"inputProfile":[{"records":1,"batches":1,"schemas":1}],"operatorId":0,"operatorType":26,"setupNanos":0,"processNanos":1020862,"peakLocalMemoryAllocated":4530432,"waitNanos":0},{"inputProfile":[{"records":1,"batches":1,"schemas":1}],"operatorId":0,"operatorType":13,"setupNanos":0,"processNanos":154675,"peakLocalMemoryAllocated":4530176,"metric":[{"metricId":0,"longValue":59}],"waitNanos":1936593}],"startTime":1464730828114,"endTime":1464730828123,"memoryUsed":0,"maxMemoryUsed":9060608,"endpoint":{"address":"zeta01.mydomain.net","userPort":20001,"controlPort":20002,"dataPort":20003},"lastUpdate":1464730828126,"lastProgress":1464730828126}]}],"user":"adm"}
Full "Broken" Profile:
{"id":{"part1":2932401029014293687,"part2":6412631480783062510},"type":1,"start":1464730828036,"end":1464730828131,"query":"alter
session set `store.parquet.enable_dictionary_encoding` =
true","foreman":{"address":"zeta01.mydomain.net","userPort":20001,"controlPort":20002,"dataPort":20003},"state":2,"totalFragments":1,"finishedFragments":0,"fragmentProfile":[{"majorFragmentId":0,"minorFragmentProfile":[{"state":3,"minorFragmentId":0,"operatorProfile":[{"inputProfile":[{"records":1,"batches":1,"schemas":1}],"operatorId":0,"operatorType":26,"setupNanos":0,"processNanos":1020862,"peakLocalMemoryAllocated":4530432,"waitNanos":0},{"inputProfile":[{"records":1,"batches":1,"schemas":1}],"operatorId":0,"operatorType":13,"setupNanos":0,"processNanos":154675,"peakLocalMemoryAllocated":4530176,"metric":[{"metricId":0,"longValue":59}],"waitNanos":1936593}],"startTime":1464730828114,"endTime":1464730828123,"memoryUsed":0,"maxMemoryUsed":9060608,"endpoint":{"address":"zeta01.mydomain.net","userPort":20001,"controlPort":20002,"dataPort":20003},"lastUpdate":1464730828126,"lastProgress":1464730828126}]}]
> 500 error when crc for a query profile is out of sync
> -----------------------------------------------------
>
> Key: DRILL-2593
> URL: https://issues.apache.org/jira/browse/DRILL-2593
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - HTTP
> Affects Versions: 0.7.0
> Reporter: Jason Altekruse
> Fix For: Future
>
>
> To reproduce, on a machine where an embedded drillbit has been run, edit one
> of the profiles stored in /tmp/drill/profiles and try to navigate to the
> profiles page on the Web UI.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
