On Jul 7, 2011, at 1:37 AM, Andrea Aime wrote:
> On Wed, Jul 6, 2011 at 5:27 PM, Yun-Hui Fan <[email protected]> wrote:
>> This one is new to me. Are the mosaic stores over a NFS or other network
>> file system?
>
> The mosaics are stored on the local drive, local to the instance of GeoServer.
>
> How are you configuring them? Are you uploading the mosaic as a zipped file
> or just poiting the
> store to a folder on disk?
We put the geotiff files that would be joined together to form the image mosaic
in a temporary directory on the local drive. Then we use REST calls to publish
those files to GeoServer so GeoServer could build or update the image mosaic
for us with those geotiff files and save the resultant mosaic in its datastore,
which is pointing to another directory on local disk. In another word, the
only reasons that we need to publish the geotiff files to GeoServer are (1) to
have GeoServer build the image mosaic for us and (2) to add the image mosaic to
GeoServer's coverages catalogue because it's in memory now. We highly suspect
it is either POST or PUT (or maybe both?) that creates those open sockets that
stay around until a restart of the instance of GeoServer.
>
>
>> What I know is that 2.1.1 leaks file descriptors at every new mosaic
>> configuration or new
>> geotiff configuration, that is being fixed:
>> http://jira.codehaus.org/browse/GEOS-4656
>> (the fixes are being checked on trunk, we should backport them on 2.1.x
>> before 2.1.2 is released)
>> The issue has no known workarounds (you can try to force GC on the virtual
>> machine, that might
>> result in the files being closed, but it's just taking a chance and hoping
>> the GC involves the
>> input streams kept open).
>
> Please excuse me for asking this really basic question. How do we force GC
> on it?
>
> What we have tried so far is adding "-XX:+UseParallelGC" in the startup
> command in startup.sh. That did not do anything for us in terms of closing
> those sockets. If there is a more direct way to force GC, we will gladly try
> it.
>
> There is a GC button (maybe it's called free memory, don't remember) in the
> status page
If it is that, then we have tried it, too. It does nothing for us in terms of
closing those sockets, either.
Thanks!
Yun-Hui
>
> Cheers
> Andrea
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
