On 6/26/2014 3:27 PM, A V Mahesh wrote:
> Hi Anders,
>
> Thank you very much for help to Tune/Configure/Fix  the IMMSV
> variables to bring-up 70 Node scalability cluster with new  MDS Multicast 
> changes.
>
> Brief note of the  MDS #851 Enhancement Ticket:
> Currently Opensaf Broadcast message was  implemented as multiple unicasts  
> (that means
> Broadcast message was reaching  N nodes  in T-1  to T-N  time based on the 
> number of 
> nodes) ,
> after the ticket #851 changes , the Opensaf Broadcast message will be 
> utilizing TIPC 
> Multicast 
> (that means message may reach  T-1   time irrelevant of  number of nodes ) .
>  
> Following list of things we have done/need to be done to bring-up 70 Node 
> cluster :
>
> 1)  Increased IMMSV_DEFAULT_FEVS_MAX_PENDING  from 16 to 255
> ------------------------------------------------------------------------------
> -#define IMMSV_DEFAULT_FEVS_MAX_PENDING 16
> +#define IMMSV_DEFAULT_FEVS_MAX_PENDING 255
> ------------------------------------------------------------------------------
>
> 2)  Adjusted the IMMSV_DEFAULT_MAX_SYNC_BATCH_SIZE to  90% of 
> MDS_DIRECT_BUF_MAXSIZE
>      to limit the A single multicast message  below fragmentation size ( 
> 65480 )
> >------------------------------------------------------------------------------------------
> -#define IMMSV_DEFAULT_MAX_SYNC_BATCH_SIZE MDS_DIRECT_BUF_MAXSIZE
> -#define IMMSV_MAX_OBJS_IN_SYNCBATCH (MDS_DIRECT_BUF_MAXSIZE/10)
> +#define IMMSV_DEFAULT_MAX_SYNC_BATCH_SIZE ((MDS_DIRECT_BUF_MAXSIZE / 100) * 
> 90)
> +#define IMMSV_MAX_OBJS_IN_SYNCBATCH (IMMSV_DEFAULT_MAX_SYNC_BATCH_SIZE / 10
> >------------------------------------------------------------------------------------------
>
> 3)  Fixed a minor bug to  reflect IMMSV_MAX_WAIT time configuration of  
> `/etc/opensaf
>/immnd.conf`
> >------------------------------------------------------------------------------------------
> -               if (jobDuration > 50) { /* No progress in 50 secs */
> +               if (jobDuration > 50 && jobDuration > immnd_cb->mWaitSecs) {  
>   /* No progress in 50 secs */
> >------------------------------------------------------------------------------------------
>
> 4)  Configured IMMSV_MAX_WAIT &  IMMSV_NUM_NODES , to take advantage of TIPC 
> Multicast
>      according to cluster size before starting Opensaf , in 
> `/etc/opensaf/immnd.conf`.
> >------------------------------------------------------------------------------------------
> export IMMSV_NUM_NODES=5  ==to===> export IMMSV_NUM_NODES=70
> export IMMSV_MAX_WAIT=3     ==to====> export IMMSV_MAX_WAIT=100
> >------------------------------------------------------------------------------------------
>
> Following list of proposals/verification to be done in the contest of  
> OpenSAF >scalability :
>
> 1)  Proposed to have wait period between consecutive sync-batches , to avoid 
> multiple
> sync-batches for periodically joining nodes ( in case of multiple payloads 
> restart after > fault or multiple payloads joining  to an existing cluster).
>
> 2) AMF need to crosscheck ,in any case the same OI handle getting shared in 
> multiple Amf > threads.If not , need to investigate why 
> `saImmOiImplementerSet() failed with ERR_EXIST > even after IMM finalize is 
> invoked before Re-initializing with IMM.
>
> -AVM


---

** [tickets:#851] MDS: use TIPC multicast**

**Status:** assigned
**Milestone:** 4.5.FC
**Created:** Mon Apr 14, 2014 09:31 AM UTC by Hans Feldt
**Last Updated:** Mon Jun 23, 2014 12:15 PM UTC
**Owner:** A V Mahesh (AVM)

MDS broadcast is implemented as multiple unicasts. This does not scale and adds 
unnecessary load to the sending process.

MDS broadcast should use TIPC multicast.

Attached is a hack that does this. It can be used to measure performance 
improvements.


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/opensaf/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/opensaf/admin/tickets/options.  Or, if this is a 
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets

Reply via email to