> When you use any Verity based technology with a cluster, you
> will have to think about how to update the clusters on other
> machines. This is NOT a show stopper, it's just something you
> have to think about. Ben Elmore had a _cool_ idea about how to
> handle this. Ben, want to describe it for the group? :)
Ben (or anyone else with similar experience), could you describe your
solution?
We've been having some problems maintaining collections for use on a
cluster. We tried file replication (updating master collections and
replicating to other machines on the cluster), but the collections became
corrupted if the replication occurred while the collections were being
updated. Our current solution is to store the collections on a network
share, so that all machines on the cluster use the same collections. The
problem with this approach is that the Windows network share only supports
2048 file handles, and the Verity collections frequently grow above this
limit. Regular optimisation of the collections helps, but its still not an
ideal solution.
Any ideas greatly appreciated.
Thanks,
Matt
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/spectra_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
