Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix uwescience/myria-web#40 #438

Merged
merged 8 commits into from
Mar 10, 2014
Merged

Fix uwescience/myria-web#40 #438

merged 8 commits into from
Mar 10, 2014

Conversation

dhalperi
Copy link
Member

@dhalperi dhalperi commented Mar 5, 2014

Fix uwescience/myria-web#40

Basically, add a column to the queries table to log the error message, if there was one, when the query executed.

Includes patches from #433 , so review after that one.

To work around #371, I added memory limits to channels. However, I made
the per-channel and the global memory limits the same. This is clearly
nuts: multiple channels can be active at the same time!

In some plans with multiple fragments that produce data, I believe that
one it is possible that one channel consumes all the memory and
deadlocks the query execution because that channel's buffer won't be
emptied until another channel on the same work is pushed.

Fix this by getting rid of the global limit.
Random code cleanup, probably comes from automatic changes?
When using the PostgreSQL COPY method, make sure the correct number of
tuples were actually inserted.
We want the appenders to see DEBUG messages; they won't actually
log them unless the code *later* sets the level to DEBUG or below.
If possible, we should print the Java that causes the failure. Before
this change:

edu.washington.escience.myria.DbException: Error when evaluating expression edu.washington.escience.myria.expression.evaluate.ConstantEvaluator@48dd0a33

After:

edu.washington.escience.myria.DbException: Error when evaluating expression (1/0)
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.0%) when pulling 24ebef5 on dhalperi-failures into 1916e37 on master.

@slxu slxu merged commit 4059168 into master Mar 10, 2014
@dhalperi dhalperi deleted the dhalperi-failures branch March 10, 2014 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Please show error messages that explain why a query got killed
3 participants