You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Sprint Team

General

Meetings

Monday February 24

Sprint Planning

Tuesday February 25

  • frank asseg

    • dealing with overhead for the SCAPE project

    • beginning to work again on the cluster and getting it operational again

  • A. Soroka
  • Greg Jansen

    • got a 7-node cluster up and running at UNC, using TCP for both discovery and state transfer

    • next step: putting it under load using benchtool

  • Ben Pennell

    • adding three params to benchtool to allow manipulating the behavior with transactions enabled

    • also benchtool now needs to track the time taken for commits

  • Mike Daines

    • having a look at authZ use cases, taking notes as to completion

    • seems to boil down to "we need to store authZ metadata and make decisions using it"

    • discussing contextual info to be used at PEPs (e.g. IP addresses)

  • Scott Prater
    • "With the help of NewRelic tech support, I was able to get all the nodes to send server and webapp metrics to the NewRelic host.  So the dashboard now shows real-time resource consumption metrics for all the nodes. I spent quite a few hours last night trying to get all the nodes to talk to each other with the NewRelic jar loaded.  I used as a base Frank's jgroups-tcp-config.xml file, which uses TCP for state transfer

      and UDP for discovery. I continued to see the same problem as I did this weekend, where after the first three nodes have connected, the last three don't;  although the other nodes see them, they don't see any other node.  I spent some time reading the relatively sparse JGroups documentation (and even sparser Infinspan documentation), and played with timeouts, number of threads, and IP address binding parameters, to no avail. That's where I'm at right now -- I can get a cluster of three nodes running, but not more (though for a brief and shining moment last night, I had five of the six nodes seeing each other.  I was unable to reproduce that state, however). Next steps:  I'm going to try to use the TCPPING and FD_SOCK methods of node discovery and detection:  the docs advocate against this for large clusters, and rightly point out that there's a large performance hit when you go from UDP to TCP, but at this point, I'm more interested in just getting a cluster that works.  That will be the focus of my efforts today. If by this afternoon I haven't made headway, I'm going to go to the JGroups list."

Wednesday February 26

Thursday February 27

Fedora Committer's Call

Friday February 28

Monday March 03

Tuesday March 04

Wednesday March 05

Thursday March 06

  • Fedora Committer Meeting
  • Sprint Wrap-up

 

  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.