Hey,
sounds like a reasonable solution to me. Please report back on your
experience?
Cheers,
Gabriel.
2012/2/22 Sebjørn Birkeland <[email protected]>
> Hi,
>
> Thank you for your response.
>
> Regarding using multiple GWC-instances with separate directories, I was
> thinking of using completely separate directories both for the metastore
> and the blobstore. This would mean that the two instances will not share
> any infomation. This will, of course, result in two tile caches. But I
> cannot see any other solution than having duplicated cache if we wish to
> have redundancy / no single point of failure. This will be exactly the same
> as deploying GWC on two different servers. It seems like this is the only
> option if we want multiple GWC-instances.
>
> Pehaps there is little actual experience in using GWC in a Weblogic
> cluster environment the same way we are trying to do. The environment
> architecture is a decision outside of our control :)
>
> Best regards,
> Sebjørn Birkeland
>
> ------------------------------
> *Fra:* [email protected] [[email protected]] på vegne av Andrea
> Aime [[email protected]]
> *Sendt:* 22. februar 2012 16:11
> *To:* Sebjørn Birkeland
> *Cc:* Gabriel Roldan; [email protected]
>
> *Emne:* Re: [Geoserver-users] Using GeoServer with shared data directory
>
> On Wed, Feb 22, 2012 at 3:58 PM, Sebjørn Birkeland <
> [email protected]> wrote:
>
>> Hi Andrea and Gabriel,
>>
>>
>> We rely on using parameterFilters for our GWC-layers, so I guess that
>> means that we cannot disable the metastore-functionality.
>> Does that mean that our only option is to use a single GWC-instance with
>> multiple GeoServer-instances? Would not this result in a single point of
>> failure?
>>
>
> I believe this is your only option at the moment. And yes, it will
> result in a single point of failure.
>
>
>>
>> Does anyone use multiple GWC-instances on Weblogic with a shared data
>> directory? Is it perhaps possible to configure the servers so that each
>> instance can use a seperate blob store directory?
>>
>
> Separate blob stores... hmmm.. this might work but you'll end up wit two
> separate tile caches too,
> as far as I remember once the metastore is enabled GWC will check the
> existance of the tile
> in the meta-store too.
>
> A solution that would require some modifications to GWC would be to have
> the metastore become
> pluggable and allow for usage of a centralized database, like a shared
> Oracle/PostgreSQL.
> And then some way for the two GWC to avoid stepping on each other toes so
> that they
> don't try to write the same tiles in parallel.
>
> 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
> mob: +39 339 8844549
>
> 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
>
> -------------------------------------------------------
>
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
