Ticket #11291 (assigned)

Opened 6 years ago

Last modified 5 years ago

Separate activemq server

Reported by: Anders Markvardsen Owned by: Lottie Greenwood
Priority: major Milestone: Backlog
Component: Tools Keywords: AUTOREDUCTION
Cc: marcus.noble@…, doucetm@… Blocked By:
Blocking: Tester:

Description (last modified by Anders Markvardsen) (diff)

At present activemq lives on the same machine that will be the worker machine for this coming cycle.

activemq will take up an unknown amount of resources on this machine, and resource requirements will only go up, e.g. with IMAT.

This ticket is to separate out activemq on a separate server, this should also help with diagnosing an activemq hardware issue from a worker hardware issue.

This ticket may be done in more than one ticket.

Steps to take:

  • Read up on best practice on activemq versus it's hardware requirements, and note SNS has now a number of years experience with activemq
  • ISIS are currently using activemq 5.8, it is time for an upgrade?
  • Request facility IT for server instance
  • Likely after this coming cycle introduce this server into production

Change History

comment:1 Changed 6 years ago by Anders Markvardsen

  • Status changed from new to assigned
  • Description modified (diff)
  • Cc marcus.noble@…, doucetm@… added
  • Keywords AUTOREDUCTION added
  • Milestone changed from Release 3.4 to Backlog
  • Owner changed from Anders Markvardsen to Lottie Greenwood

comment:2 Changed 5 years ago by Anders Markvardsen

From speaking to Nick (Draper), a basic entry VM should be sufficient, with activeMQ itself not requiring more than 1-2GB and few cores.

Worse looking to see if ActiveMQ has a persistance option, that is if it is restarted is has kept a record of the queues.

Note: See TracTickets for help on using tickets.