GitHub user zcorrea opened a pull request:

    https://github.com/apache/trafodion/pull/1457

    [TRAFODION-2883] Preliminary Scale Enhancements

    - Added timestamps to node down system message
    - Added timestamps and values to registry change notifications
    - Fixed monitor trace causing memory overwrites
    - Implemented AGENT mode monitor functionality
          o This is a pre reliminary change to remove dependency on OpenMPI 
during 
            initialization of operational cluster by creating a cluster of one 
node 
            (MASTER monitor) where other remote nodes (SLAVE monitors) join the 
            cluster through the MASTER
    - Implemented MASTER monitor selection logic
    - Scale bug fixes found when creating clusters greater than 120 nodes-


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zcorrea/trafodion TRAFODION-2883

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/trafodion/pull/1457.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1457
    
----
commit 887051c8a1ba57b0ad47278dce2fc9361a2afb9c
Author: Zalo Correa <zalo.correa@...>
Date:   2018-02-21T00:57:40Z

    [TRAFODION-2883] Preliminary Scale Enhacements
    - Increased cluster node limit to 1024
    - Added timestamps to node down system message
    - Added timestamps and values to registry change notifications
    - Fixed monitor trace causing memory overwrites

commit bded0e843f8b600a5459c5353bbdc9f59d6d6551
Author: Zalo Correa <zalo.correa@...>
Date:   2018-02-28T01:34:25Z

    [TRAFODION-2883] Preliminary Scale Enhacements
    - Added timestamps to node down system message
    - Added timestamps and values to registry change notifications
    - Fixed monitor trace causing memory overwrites
    - Implemented AGENT mode monitor functionality
          o This is a pre reliminary change to remove dependency on OpenMPI 
during
            initialization of operational cluster by creating a cluster of one 
node
            (MASTER monitor) where other remote nodes (SLAVE monitors) join the
            cluster through the MASTER
    - Implemented MASTER monitor selection logic
    - Scale bug fixes found when creating clusters greater than 120 nodes-

----


---

Reply via email to