Bug 542019

Summary: fix integration problem to allow cluster2 to potentially scale to 48 nodes
Product: Red Hat Enterprise Linux 5 Reporter: Steven Dake <sdake>
Component: cmanAssignee: Christine Caulfield <ccaulfie>
Status: CLOSED NOTABUG QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 5.4CC: cluster-maint, edamato
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 542018 Environment:
Last Closed: 2009-12-07 09:00:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 542018    
Bug Blocks:    
Attachments:
Description Flags
Patch to add nodeids to objdb none

Description Steven Dake 2009-11-27 23:40:35 UTC 
+++ This bug was initially created as a clone of Bug #542018 +++

Description of problem:
totem delivers partial membership events in large clusters which causes cman to enter "disallowed node state"

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. start 48 node cluster
2. kill 16 nodes
3. cluster self destructs
  
Actual results:
cluster enters disallowed node state

Expected results:
this state should rarely happen.

Additional info:
Comment 1 Steven Dake 2009-11-27 23:41:23 UTC 
need changes to cman to setup objdb to contain node ids.
Comment 2 Steven Dake 2009-11-27 23:43:24 UTC 
lets fix in corosync/cluster3 and agree on the model before backporting.
Comment 4 Christine Caulfield 2009-12-02 15:03:33 UTC 
Created attachment 375452 [details]
Patch to add nodeids to objdb

This is the proposed cman patch to do the job, depending on how we agree to store the nodeids in the objdb.

Even if we don't agree on this format, the patch will only need small changes.
Comment 5 Christine Caulfield 2009-12-07 09:00:26 UTC 
This bug has been superseded by

https://bugzilla.redhat.com/show_bug.cgi?id=544482