[daisy] Scaling Daisy

[Shon Schetnan]

John,

Thanks for the input!

I am curious.  Have you tried or heard of anyone trying to hookup the Daisy repsitory server to a SAN drive and pointing multiple server instances at it?  A couple of us here were discussing this and wondering if that might be a solution?  Any thoughts?

Shon


On 12/10/07 11:36 AM, "Kealy, John" <John.Kealy at ucsf.edu> wrote:

Shon,

As far as I know the repository server is the java virtual machine
interacting with (primarily) the daisy data portion of your file system
(blob store, ect) and the MySQL database. We have a primary and failover
set up at UCSF. We use a slave database and rsync the daisydata
directory to our fail over server. We  do not allow writing on the fail
over server. It is in place only to assure read continuity not write
continuity..

We are having some trouble with our f-5 load balancers working with the
wiki portion of daisy. Our load balancers do not have the latest version
of the F-5 OS (9.4.3) and the version we are running (9.0.5) has some
problems with multipart HTTP transactions. We are looking to upgrade
early next year and will try to keep everyone in the loop.

There was some discussion about very large data sets on the list back in
march of this year. There didn't seem to be a resolution to the thread
but you can check it out at:
http://www.nabble.com/issue-with-large-amout-of-documents-to9692006.html
#a9692006

Base on those results it seems that you can simply allocate more RAM to
the repository and alter the document cache setting to solve some
problems at the low end of the scale problem (collections of less than
100,000 documents)....

We are still working on solving this problem of high availability as
it's important for us to have 24/7 availability of our systems at UCSF.

Cheers,

John Kelay


-----Original Message-----
From: daisy-bounces at lists.cocoondev.org
[mailto:daisy-bounces at lists.cocoondev.org] On Behalf Of Shon Schetnan
Sent: Monday, December 10, 2007 7:57 AM
To: daisy at lists.cocoondev.org
Subject: [daisy] Scaling Daisy

Hello,

I am new to Daisy.  We are considering Daisy to be the
repository/content manager for our web application.  Daisy seems to fit
our problem very well functionally as it is the repository that matters
most to us, and I love the flexible composite document structure that
Daisy provides.  That helps solve a problem that we have for versioning
product like information.

I am concerned about how to Scale Daisy.  I haven't seen any
documentation on the subject, and browsing through the mailing list
archives, there seems to be some talk that suggests that Daisy may not
be able to scale beyond one repository server.  I have a couple
questions.

1.  What does this mean exactly ( repository server )?  The Java server,
or the MySQL database?

2.  Has anyone tried load balancing the product across F5 load
balancers?

3.  How have others in the community solved the load balancing/high
availability problem?

Thanks,

Shon


This message is intended only for the use of the individual or entity to
whom it is addressed, and may contain information that is PROPRIETARY
and CONFIDENTIAL. If you are not the intended recipient or the employee
or agent responsible for delivering the message to the intended
recipient, you are hereby notified that any dissemination, distribution,
or copying of this communication is strictly prohibited. If you have
received this communication in error, please notify the above named
sender at the above telephone number.
_______________________________________________
daisy community mailing list
Professional Daisy support:
http://outerthought.org/site/services/daisy/daisysupport.html
mail to: daisy at lists.cocoondev.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/site/services/daisy/daisysupport.html
mail to: daisy at lists.cocoondev.org
list information: http://lists.cocoondev.org/mailman/listinfo/daisy



________________________________
This message is intended only for the use of the individual or entity to whom it is addressed, and may contain information that is PROPRIETARY and CONFIDENTIAL. If you are not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the above named sender at the above telephone number.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cocoondev.org/pipermail/daisy/attachments/20071211/3edad770/attachment.htm