Are you asking Pravin or Rajiv (the original reporter)? For Pravin's case we no longer have the issue as we now guarantee we have clean index builds before they are queried against -- but we had determined for one segfault case was when we were querying against incomplete failed index builds (e.g. in testing we encountered disk exhaustion) that we allowed to be used.
On Fri, Jul 25, 2014 at 10:36 AM, K. John Wu <[email protected]> wrote: > Hi, Pravin, > > Would you mind say a few words more about the use case that led to SIG > fault? I am curious to see if there is a quick solution to it. > > Thanks. > > John > > > > On 7/23/14 2:04 PM, Pravin Joshi wrote: > > Rajiv, > > > > What FastBit version you using? I used 3.1.8 and encountered SIGSEGV if > > index is not created properly. I would suggest taking a look at > > column definition and make sure the column you are fetching is defined as > > Long. > > > > > > Pravin > > > > > > On Wed, Jul 23, 2014 at 1:57 PM, Rajiv Bandaru <[email protected]> > > wrote: > > > >> > >> This is the another error... > >> > >> > >> # > >> # A fatal error has been detected by the Java Runtime Environment: > >> # > >> # SIGSEGV (0xb) at pc=0x00007f957c64f33a, pid=16202, > tid=140280209815296 > >> > >> # > >> # JRE version: 6.0_25-b06 > >> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.0-b11 mixed mode > >> linux-amd64 compressed oops) > >> # Problematic frame: > >> # v ~BufferBlob::jni_fast_GetLongField > >> > >> # > >> # An error report file with more information is saved as: > >> # /home/rajiv.bandaru/sir/bin/hs_err_pid16202.log > >> > >> # > >> # If you would like to submit a bug report, please visit: > >> # http://java.sun.com/webapps/bugreport/crash.jsp > >> # The crash happened outside the Java Virtual Machine in native code. > >> # See problematic frame for where to report the bug. > >> # > >> Aborted (core dumped) > >> > >> On Wed, Jul 23, 2014 at 1:15 PM, Rajiv Bandaru <[email protected]> > >> wrote: > >> > >>> I am running a particular fastbit query continuously for 10 minutes, > >>> however the process crashes with the following native code errors. I am > >>> running it on Ubuntu. > >>> > >>> > >>> # > >>> # A fatal error has been detected by the Java Runtime Environment: > >>> # > >>> # SIGSEGV (0xb) at pc=0x00007f35d009ae84, pid=13865, > tid=139869078443776 > >>> # > >>> # JRE version: 6.0_25-b06 > >>> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.0-b11 mixed mode > >>> linux-amd64 compressed oops) > >>> # Problematic frame: > >>> # C [libpthread.so.0+0x9e84] pthread_mutex_lock+0x4 > >>> # > >>> # An error report file with more information is saved as: > >>> # /home/rajiv.bandaru/sir/bin/hs_err_pid13865.log > >>> # > >>> # If you would like to submit a bug report, please visit: > >>> # http://java.sun.com/webapps/bugreport/crash.jsp > >>> # The crash happened outside the Java Virtual Machine in native code. > >>> # See problematic frame for where to report the bug. > >>> # > >>> Aborted (core dumped) > >>> > >>> > >>> And, the second error is exactly the same but here is the Problematic > >>> frame > >>> > >>> BufferBlob::jni_fast_GetLongField > >>> > >>> > >>> Rajiv > >>> > >> > >> > >> _______________________________________________ > >> FastBit-users mailing list > >> [email protected] > >> https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users > >> > >> > > > > > > > > _______________________________________________ > > FastBit-users mailing list > > [email protected] > > https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users > > > _______________________________________________ > FastBit-users mailing list > [email protected] > https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users >
_______________________________________________ FastBit-users mailing list [email protected] https://hpcrdm.lbl.gov/cgi-bin/mailman/listinfo/fastbit-users
