I am looking at the GC logs for some big queries (now that I know how to
enabled them, thanks Paul!) and found the item below, it worries, "it
says, failure, it too 8 seconds) Should I be worried about that? I know my
HEAP is set fairly high (24GB) how should I interpret this?
John
1924.138: [G
Also: Doing a CTAS using the new reader and dictionary encoding is
producing this, everything is hung at this point. The query in sqlline is
not returning, the web UI is running extremely slowly, and when it does
return, shows the running query, however, when I click on it, the profile
shows an err
Oh, the query just stopped showing up in the profiles webui, completely
gone like it never happened. Seems to be responding a bit better, the
sqlline is still hung though.
(Yes this is all related to my CTAS of the parquet data, at this point I am
just looking for ways to handle the data and not m
My understanding (which is incomplete) is that both the "new reader" and
"dictionary encoding" are not stable yet and can cause failures or worse,
incorrect data. That's why they are disabled by default.
The "Allocation Failure" means that the JVM had to run a Full GC because it
couldn't allocate
It's just a flat select (via a view) . basically select field1, field2,
field100 from view_mytable where dir0 = '2016-05-01' there is no
aggregation or anything happening.
As to the dictionary encoding and the new reader some thoughts:
1. Based on what I've read, the new reader is faster for
