Open GoogleCodeExporter opened 9 years ago
I assume that the CC and the NC are on the same box, is that right?
Original comment by westm...@gmail.com
on 30 May 2014 at 1:59
mvn package on that branch hangs for me (after a number of NPEs in the log).
Is that expected?
Original comment by westm...@gmail.com
on 30 May 2014 at 2:29
I was using a separate machine for the CC.
For your second question, I actually never tried to run the tests on this
branch. It is maintained mainly by Zack and Young-Seok. So I will let one of
them answer this question.
Original comment by salsuba...@gmail.com
on 30 May 2014 at 2:35
There was some hacking that was required in order to get numbers so don't
expect all of the tests to pass. If you give me the NPE, I can tell you whether
or not that particular error is expected or not. My guess is that it is related
to feeds and/or parsing.
Original comment by zheilb...@gmail.com
on 30 May 2014 at 3:35
NPEs look like this - they are available with different stacks on top of the
IOManager
edu.uci.ics.hyracks.api.exceptions.HyracksDataException:
java.lang.NullPointerException
at edu.uci.ics.hyracks.storage.am.common.dataflow.IndexBulkLoadOperatorNodePushable.close(IndexBulkLoadOperatorNodePushable.java:92)
at edu.uci.ics.hyracks.dataflow.std.sort.ExternalSortRunMerger.process(ExternalSortRunMerger.java:164)
at edu.uci.ics.hyracks.dataflow.std.sort.ExternalSortOperatorDescriptor$MergeActivity$1.initialize(ExternalSortOperatorDescriptor.java:189)
at edu.uci.ics.hyracks.api.rewriter.runtime.SuperActivityOperatorNodePushable.initialize(SuperActivityOperatorNodePushable.java:81)
at edu.uci.ics.hyracks.control.nc.Task.run(Task.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at edu.uci.ics.hyracks.control.nc.io.IOManager.sync(IOManager.java:241)
at edu.uci.ics.hyracks.storage.common.buffercache.BufferCache.force(BufferCache.java:787)
at edu.uci.ics.hyracks.storage.am.lsm.common.impls.AbstractLSMIndex.forceFlushDirtyPages(AbstractLSMIndex.java:114)
at edu.uci.ics.hyracks.storage.am.lsm.btree.impls.LSMBTree.markAsValid(LSMBTree.java:533)
at edu.uci.ics.hyracks.storage.am.lsm.common.impls.LSMHarness.addBulkLoadedComponent(LSMHarness.java:345)
at edu.uci.ics.hyracks.storage.am.lsm.btree.impls.LSMBTree$LSMBTreeBulkLoader.end(LSMBTree.java:606)
at edu.uci.ics.hyracks.storage.am.common.dataflow.IndexBulkLoadOperatorNodePushable.close(IndexBulkLoadOperatorNodePushable.java:90)
... 7 more
Original comment by westm...@gmail.com
on 30 May 2014 at 5:32
Okay, this looks foreign to me. It doesn't look related to a change that we
made for the experiments.
Original comment by zheilb...@gmail.com
on 30 May 2014 at 6:14
I think that the NPE is related to the IO profiling code that counts the number
of buffer evictions.
As long as there is only one running NC in a machine, the NPE doesn't occur.
However, the ExecutionTest uses two NCs, so it causes the NPE.
Sattam may know more than me regarding the buffer eviction count code since he
added the code there. :)
The following shows the corresponding code change links.
1. Hyracks:
https://code.google.com/p/hyracks/source/detail?r=0bd44d82c7a2bdaf1e36a58b53ca93
c896f5a402&name=lsm_storage_experiments
2. Asterix:
https://code.google.com/p/asterixdb/source/detail?r=9dee7f0d1b2b2c5afc70928562b9
d811e6b1687c&name=lsm_storage_experiments
--> Among the changed sources in Asterix, JobEventListenerFactory.java is the
only source code directly related to the buffer eviction count.
Original comment by kiss...@gmail.com
on 30 May 2014 at 4:03
Ah, now I remember :-)
Yes, I added this code to collect performance numbers a while ago, and it is
quite possible to cause errors when running the tests.
So please ignore the failing test cases.
Original comment by salsuba...@gmail.com
on 30 May 2014 at 4:07
Or if you prefer, you could locally revert the changes that Young-Seok shared
for both hyracks and asterix.
Original comment by salsuba...@gmail.com
on 30 May 2014 at 4:08
Status: There has been some investigation, but I was not able to identify or
reliably reproduce the issue.
Original comment by westm...@gmail.com
on 30 Jul 2014 at 4:34
Original issue reported on code.google.com by
salsuba...@gmail.com
on 29 May 2014 at 10:45