Skip to content

Instantly share code, notes, and snippets.

@ajayhn

ajayhn/analytics-on-separate-db-node.md

Created June 22, 2016 20:42
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ajayhn/ef309e9ec99ea3eb44f466b275a0d2bd to your computer and use it in GitHub Desktop.
Save ajayhn/ef309e9ec99ea3eb44f466b275a0d2bd to your computer and use it in GitHub Desktop.
Download ZIP
analytics-on-separate-db-node
Raw
analytics-on-separate-db-node.md

  1. Install 3 new servers with base OS same s4,5,6

  2. Install analytics and database packages on the 3 new servers s4,5,6

    • which packages kafka too?

  3. service supervisor-analytics stop; service cassandra stop; kafka?

  4. Determine whether old analytics DB is to be migrated or built anew 4.1 To be anew 4.1.1 service supervisor-analytics stop on s1,2,3 4.1.2 provision cassandra.yaml and cassandra-env.sh to have a cluster of s4,5,6 4.1.3 provision analytics processes - discovery-ip should be VIP. 4.1.4 service supervisor-analytics start; service cassandra start; kafka?

    4.2 To migrate from old 4.2.1 Northbound shutoff - stop supervisor-config supervisor-analytics 4.2.2 Take a cassandra snapshot 4.2.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment