It appears that if the first brick in a replicated/distributed configuration is rebooted or suffers some sort of a temporary issue, it both means that the system doesn't appear to be dropped after 10 seconds from the cluster and also that after it comes back up, pending transactions have issues for the next 10 minutes or so. Is this a locks issue or is this a bug? Justice London E-mail: jlondon at lawinfo.com
