会员体验
专利管家(专利管理)
工作空间(专利管理)
风险监控(情报监控)
数据分析(专利分析)
侵权分析(诉讼无效)
联系我们
交流群
官方交流:
QQ群: 891211   
微信请扫码    >>>
现在联系顾问~
热词
    • 1. 发明授权
    • Method and system for transparently failing over application configuration information in a server cluster
    • 在服务器集群中透明地将应用配置信息故障的方法和系统
    • US06360331B2
    • 2002-03-19
    • US09061857
    • 1998-04-17
    • John D. VertSunita Shrivastava
    • John D. VertSunita Shrivastava
    • H02H305
    • G06F11/1662G06F11/203G06F11/2038H04L1/22
    • A method and system for transparently failing over a legacy application from a first system to a second system of a server cluster by tracking and checkpointing changes to application configuration information stored in a system's local registry. When an application running on the first system makes a change to the application configuration information in a subtree of the registry, the change is detected and a snapshot of the subtree's data is taken. The snapshot is written to a storage device shared by systems of the cluster, such as a quorum disk. When the application is failed over to a second system, the snapshot for that application is retrieved from the quorum disk and written to the registry of the second system in a corresponding subtree. The application is then run on the second system using the most-recent application configuration information as modified by the other system in the cluster.
    • 通过跟踪和检查点对存储在系统的本地注册表中的应用程序配置信息的更改来将传统应用程序从第一系统透明地故障转移到服务器集群的第二系统的方法和系统。 当在第一系统上运行的应用程序更改注册表的子树中的应用程序配置信息时,检测到更改,并获取子树数据的快照。 该快照将写入由集群系统共享的存储设备,例如仲裁磁盘。 当应用程序故障切换到第二个系统时,该应用程序的快照从仲裁磁盘检索,并写入相应子树中的第二个系统的注册表。 然后使用群集中其他系统修改的最新应用程序配置信息在第二个系统上运行该应用程序。
    • 2. 发明授权
    • Method and system for discarding locally committed transactions to ensure consistency in a server cluster
    • 丢弃本地提交的事务的方法和系统,以确保服务器集群的一致性
    • US06449734B1
    • 2002-09-10
    • US09062211
    • 1998-04-17
    • Sunita ShrivastavaJohn D. Vert
    • Sunita ShrivastavaJohn D. Vert
    • H02H305
    • G06F11/1662G06F11/1425G06F17/30371Y10S707/99938
    • A method and system for forming a new cluster of servers having state data that is consistent with the state data of a cluster that previously existed. The previous cluster preserves its state data by recording transactions to a log file in conjunction with a sequence number maintained by each node. The node that recorded the transaction then increments its copy of the sequence number and attempts to replicate the transaction to other nodes of the cluster. If the transaction is replicated, each other node commits the transaction and increments its sequence number. If the node fails before it can replicate the transaction, then no other nodes will increment their sequence numbers, whereby the next logged transaction has the same sequence number as the previously logged, but orphaned replicated transaction. When a new node forms a cluster, it unrolls the log file so as to become consistent with the state of the previous cluster. Logged transactions having duplicate sequence numbers indicate that the first such transaction was not fully replicated. To remain consistent, the first transaction is discarded and not used to update the state of the new cluster.
    • 一种用于形成具有状态数据的新的服务器集群的方法和系统,该状态数据与先前存在的集群的状态数据一致。 先前的集群通过将事务记录到日志文件中并通过每个节点维护的序列号来保留其状态数据。 记录事务的节点然后增加其序列号的副本,并尝试将事务复制到集群的其他节点。 如果事务被复制,则每个其他节点提交事务并递增它的序列号。 如果节点在复制事务之前失败,则其他节点将不会增加其序列号,从而下一个记录的事务与先前记录但是孤立的复制事务具有相同的序列号。 当一个新节点形成一个集群时,它会展开该日志文件,以便与上一个集群的状态保持一致。 具有重复序列号的记录事务表明第一个此类事务未完全复制。 为了保持一致性,第一个事务被丢弃,不用于更新新集群的状态。
    • 3. 发明授权
    • Method and system for replicated and consistent modifications in a
server cluster
    • 在服务器集群中进行复制和一致修改的方法和系统
    • US6163855A
    • 2000-12-19
    • US62359
    • 1998-04-17
    • Sunita ShrivastavaRod GamacheJohn D. Vert
    • Sunita ShrivastavaRod GamacheJohn D. Vert
    • G06F11/00
    • G06F11/1443G06F2201/82
    • A method and system for communicating modification information to servers in a server cluster. Local changes, such as modifications to a resource requested at one node, are associated into a single transaction. A master node, such as the node that owns the set of resources corresponding to the modifications in the transaction requests permission from a locker node to replicate the transaction. When permission to replicate the transaction is received from the locker node, the master node replicates the transaction by requesting each node in the cluster, one node at a time, to commit the transaction. Any node that does not commit the transaction is removed from the cluster, ensuring consistency of the cluster. Failure conditions of any node or nodes are also handled in a manner that ensures consistency.
    • 用于将修改信息传送到服务器集群中的服务器的方法和系统。 本地更改(例如对在一个节点请求的资源的修改)与单个事务相关联。 主节点(例如拥有与事务中的修改相对应的资源集合的节点)从存储器节点请求许可以复制事务。 当从更衣室节点接收到复制事务的权限时,主节点通过请求集群中的每个节点(一次一个节点)来提交事务来复制事务。 任何未提交事务的节点都将从集群中删除,以确保集群的一致性。 任何节点或节点的故障条件也以确保一致性的方式进行处理。
    • 4. 发明授权
    • Failover scopes for nodes of a computer cluster
    • 计算机集群节点的故障转移范围
    • US07451347B2
    • 2008-11-11
    • US10962010
    • 2004-10-08
    • Chittur P. SubbaramanSunita Shrivastava
    • Chittur P. SubbaramanSunita Shrivastava
    • G06F11/00
    • G06F11/2023G06F11/2028G06F11/2035
    • A failover scope comprises a node collection in a computer cluster. A resource group (e.g., application program) is associated with one or more failover scopes. If a node fails, its hosted resource groups only failover to nodes identified in each resource group's associated failover scope(s), beginning with a first associated failover scope, in order, thereby defining an island of nodes within which a resource group can failover. If unable to failover to a node of a resource group's first failover scope, failover is attempted to a node represented in any next associated failover scope, which may require manual intervention. Failover scopes may represent geographic sites, whereby each resource group attempts to failover to nodes within its site before failing over to another site. Failover scopes may be managed by the cluster runtime automatically, e.g., an added node is detectable as belonging to a site represented by a failover scope.
    • 故障转移范围包括计算机集群中的节点集合。 资源组(例如,应用程序)与一个或多个故障切换范围相关联。 如果一个节点出现故障,则其托管的资源组只能按顺序从第一个关联的故障切换范围开始故障转移到从每个资源组的关联故障切换范围中识别的节点,从而定义资源组可以在其中进行故障切换的节点岛。 如果无法故障切换到资源组的第一个故障转移范围的节点,则会尝试在任何下一个关联的故障切换范围中表示的节点进行故障转移,这可能需要手动干预。 故障转移范围可以表示地理站点,由此每个资源组都尝试故障切换到其站点内的节点,然后再故障转移到另一个站点。 故障转移范围可以由集群运行时自动管理,例如,添加的节点可被检测为属于由故障转移范围表示的站点。