Re: What happens when persistent outrigger gets full

Gary Kendall <[email protected]>
Newsgroups gmane.comp.java.sun.javaspaces
Message-ID <[email protected]>
>>
>>As expected, I've managed to exceed the 2GB limit of PSE Pro for the
>>persistent space. However, to my surprise, the space has carried on
>working.
>>The only problem is that I now have many LogStore entries that are no
>longer
>>getting consolidated into the PSE file.
>>
>>
>A couple of things. First, we are not aware of a 2GB limitation for
>PSEPro. It does keep
>all of the objects in one file, so you could be running into a
>filesystem level 2GB limit
>(of course in practice the fact that Outrigger caches everything in
>memory make running
>out of memory a much more likely problem).

I remember the 2GB limit when I was developing with PSE Pro myself a few
years ago. There was no memory problem because I was running with a 4GB heap
using the 64 bit JVM.

In fact I've run spaces with a much larger PSE file than the Java heap
available, so I'm not sure that memory always limits us.

In fact the space appeared to behave normally until it was restarted. It
then failed to consolidate the logs into the PSE file and did not recognize
any of the entries that were created after the PSE file got full.

As far as requests for enhancement are concerned, it would be good if
outrigger could handle a space > 2GB!

Thanks,

Gary.

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff JAVASPACES-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

To view past JAVASPACES-USERS postings, please see:
http://archives.java.sun.com/archives/javaspaces-users.html

JDC members can download the JavaSpaces(tm) Technology from:
http://developer.java.sun.com/developer/products/jini/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.