Apps/ServerArchitecture: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 51: Line 51:
* Servers
* Servers
** appsync-hbase-stage1.vm1.labs.sjc1.mozilla.com
** appsync-hbase-stage1.vm1.labs.sjc1.mozilla.com
*** "master": running the namenode
*** Zookeeper quorum node
*** Also running as an HDFS data node and HBase region server
** appsync-hbase-stage2.vm1.labs.sjc1.mozilla.com
** appsync-hbase-stage2.vm1.labs.sjc1.mozilla.com
*** "slave": running HDFS data node and HBase region server
*** Zookeeper quorum node
* stack
* stack
** CentOS6
** CentOS6
** ?
** Sun JVM 1.6.0
** Cloudera HBase distro version CDH3U2
* status - DEPLOYED
* status - DEPLOYED
* CI / CD - ?
* CI / CD - none


= open questions =
= open questions =

Revision as of 18:29, 6 December 2011

appsync.png


appsync/myapps

memcached

  • Points of contact
    • Ops: Gozer
    • appsync-stage1.vm1.labs.sjc1.mozilla.com
  • stack
    • CentOS 6
    • Python 2.6
    • nginx
    • gunicorn
    • appsync server
  • status - DEPLOYED

Sauropod Node.JS server ?

  • Points of contact
    • Ops: Gozer
    • Devs: ?
  • Servers
    • sauropod-stage1.vm1.labs.sjc1.mozilla.com
  • stack
    • CentOS6
    • ?
  • status - ?
  • CI / CD - ?

Sauropod HBAse stack

  • Points of contact
    • Ops: Gozer
    • Devs: rtilder
  • Servers
    • appsync-hbase-stage1.vm1.labs.sjc1.mozilla.com
      • "master": running the namenode
      • Zookeeper quorum node
      • Also running as an HDFS data node and HBase region server
    • appsync-hbase-stage2.vm1.labs.sjc1.mozilla.com
      • "slave": running HDFS data node and HBase region server
      • Zookeeper quorum node
  • stack
    • CentOS6
    • Sun JVM 1.6.0
    • Cloudera HBase distro version CDH3U2
  • status - DEPLOYED
  • CI / CD - none

open questions

  • how to load balance sauropod ? client-side ? Zeus ?
  • backup on the sauropod nodes ?