Subject | Vulcan architecture and lock tables |
---|---|
Author | Dmitry Yemanov |
Post date | 2006-12-15T17:15:07Z |
All,
In Vulcan, we may have a few engine providers within a single
installation. It's supposed that every of them is responsible for each
own ODS. The problem is that each engine provider may have different
(read: incompatible) lock manager implementation. As all providers by
default share the same root directory (and hence the lock table), an
attempt to use them simultaneously would cause server crashes and
database corruptions. Am I missing something or is it a real problem? If
the latter, how are we going to guarantee the consistency? Also, even if
all engines are configured for different roots, this issue implies that
one would need a few versions of fb_lock_print in order to analyze the
lock table.
Comments?
Dmitry
In Vulcan, we may have a few engine providers within a single
installation. It's supposed that every of them is responsible for each
own ODS. The problem is that each engine provider may have different
(read: incompatible) lock manager implementation. As all providers by
default share the same root directory (and hence the lock table), an
attempt to use them simultaneously would cause server crashes and
database corruptions. Am I missing something or is it a real problem? If
the latter, how are we going to guarantee the consistency? Also, even if
all engines are configured for different roots, this issue implies that
one would need a few versions of fb_lock_print in order to analyze the
lock table.
Comments?
Dmitry