Eason Zhang commented on TRAFODION-2884:

Is there a flow chart for the startup process?

Some questions:
 # In the past, we use sqshell -> startup command to call mpirun and start 
monitor process on all nodes. For now it seems we don't rely on mpirun anymore, 
so who will start the monitor process itself? 
 # When the monitor process is started, it will start the name server process 
if it is configured to have one. Then how does other name server process 
connect to this one? Who will bring up the name server process on the other 
 # How will the name server bring up the monitor process on all nodes?

> Trafodion Foundation Scalability Enhancements
> ---------------------------------------------
>                 Key: TRAFODION-2884
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2884
>             Project: Apache Trafodion
>          Issue Type: Improvement
>          Components: dtm, foundation, installer
>    Affects Versions: 2.3
>            Reporter: Gonzalo E Correa
>            Assignee: Gonzalo E Correa
>            Priority: Major
>             Fix For: 2.3
>         Attachments: 
> TRAFODION-2884-Scalable_Name_Space-Architecure-review.v2.2.pdf, 
> TRAFODION-2884-Scalable_Name_Space-Architecure.v1.0.pdf, 
> TRAFODION-2884-Scalable_Name_Space-Architecure.v1.1.pdf, 
> TRAFODION-2884-Scalable_Name_Space-Architecure.v2.0.pdf, 
> TRAFODION-2884-Scalable_Name_Space-Architecure.v2.1.pdf, 
> TRAFODION-2884-Scalable_Name_Space-Architecure.v2.2.pdf, 
> TRAFODION-2884-Scalable_Name_Space-DesignNotes-review.v1.0.pdf, 
> TRAFODION-2884-Scalable_Name_Space-DesignNotes.v0.1.pdf, 
> TRAFODION-2884-Scalable_Name_Space-DesignNotes.v1.0.pdf
> Architectural changes are needed in the Trafodion Foundation components to 
> effectively scale above 256 servers.

This message was sent by Atlassian JIRA

Reply via email to