I'm seeing more unrecoverable errors.
All the problems have occurred during updates.
Reviewing the forums/bug tracking, it seems like this problem may have been
resolved.
Rather than spending the effort recreating the error with mock data, I will
wait for the next stable release.
If the next stable release does not resolve the issue, then I will invest
time recreating the error with a regression test scenario.
In the meantime, I have limited the number of update threads in an effort to
minimize the impact.
More background:
* All the databases having issues are larger than 2 GB on the drive.
* The memory is limited to Amazon micro-instance (3200 blocks allocated to
SEDNA)
* Numerous connections conducting read and updates against a single db
instances.
* Updates are significant in nature, not 1 or 2 nodes, but hundreds of nodes
over multiple documents.
* All the documents have multiple indexes.
Thanks,
Malcolm
------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
Sedna-discussion mailing list
Sedna-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sedna-discussion
