Hi, Deepa,

I would guess that you are using data generated by setqgen.  Would you
mind tell us how many rows are there?  What are the exact queries
you've used?

I would assume that your join is a little too big to be held in 1GB of
memory.  If you give me the about information, I would be able to
confirm this speculation.

John



On 5/25/12 1:07 PM, Deepa Sahni wrote:
> 
> Hi John,
> 
> I have attached the data partition details of all the columns. The
> issue I am having is with the following columns.
> 
> Column Name                  Issue
> --------------------------------------------------
> k4                                   killed
> k10                                 killed
> k10k                               segmentation fault
> k100                               segmentation fault
> 
> In addition to this I am running FastBit on ubuntu(running on top of
> VMPlayer) and the ram available to it is 1GB and hard disk is 20GB.
> If you need any other information I will provide that too.
> 
> Thanks,
> Deepa
> 
> 
> 
> On Fri, May 25, 2012 at 9:36 AM, K. John Wu <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     Yes, you are probably encounter memory shortage.  Since you did not
>     give any size information, there is no way for me to verify your
>     statement;-)
> 
>     John
> 
> 
>     On 5/25/12 1:09 AM, Deepa Sahni wrote:
>     > Hi,
>     >
>     >  I need some help debugging an issue. FYI I am running FastBit on
>     > ubuntu.
>     >
>     > Whenever I run queries with certain columns in the where clause
>     I get
>     > the following errors.
>     >
>     > for column K100 : Process killed
>     > for column K10 :Segmentation Fault
>     >
>     > I did not create indexes on any of the columns, since my
>     understanding
>     > was that FastBit creates indexes as and when needed. As I ran my
>     > queries indexes got created. But for the columns mentioned above I
>     > repeatedly get the same error for all select statements with these
>     > columns in the where clause.
>     >
>     > I tried deleting all the other indexes to clear up some memory for
>     > these(K100, K10) column indexes(I think this might be happening
>     > because of memory shortage). It did not fix the problem. Could some
>     > shed some light on what might be causing this error or how to
>     debug or
>     > fix this.
>     >
>     >
>     >         Thanks in advance,
>     >         Deepa
>     >
>     >
>     >
>     >
>     >
>     > _______________________________________________
>     > FastBit-users mailing list
>     > [email protected] <mailto:[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

Reply via email to