Change Details

`wdqs-categories` , a separate blazegraph instance which powers [[ https://wikitech.wikimedia.org/wiki/Nova_Resource:Catgraph/Deepcat | the deepcat service ]] , is currently deployed alongside the primary blazegraph instance (`wdqs-main` or `wdqs-scholarly`) on all WDQS hosts. Since we split the primary blazegraph instance itself in T337013, we've started wondering about how to handle `wdqs-categories`. Do we... - continue to run it on all hosts? - migrate it to its own environment? -- If we migrate, would it be VMs or Kubernetes? Creating this ticket to discuss why might want to move this service (easier to operate? fewer resources?) , level of effort involved with the status quo vs. migration, etc. If we do decide to migrate, we'll handle the work in a subsequent ticket.

`wdqs-categories` , a separate blazegraph instance which powers [[ https://wikitech.wikimedia.org/wiki/Nova_Resource:Catgraph/Deepcat | the deepcat service ]] , is currently deployed alongside the primary blazegraph instance (`wdqs-main` or `wdqs-scholarly`) on all WDQS hosts. We suspect this service may have contributed to an outage (see T374009 for more details). Since we split the primary blazegraph instance itself in T337013, we've started wondering about how to handle `wdqs-categories`. Do we... - continue to run it on all hosts? - migrate it to its own environment? -- If we migrate, would it be VMs or Kubernetes? Creating this ticket to discuss why might want to move this service (easier to operate? fewer resources?) , level of effort involved with the status quo vs. migration, etc. If we do decide to migrate, we'll handle the work in a subsequent ticket.

`wdqs-categories` , a separate blazegraph instance which powers [[ https://wikitech.wikimedia.org/wiki/Nova_Resource:Catgraph/Deepcat | the deepcat service ]] , is currently deployed alongside the primary blazegraph instance (`wdqs-main` or `wdqs-scholarly`) on all WDQS hosts. We suspect this service may have contributed to an outage (see T374009 for more details). Since we split the primary blazegraph instance itself in T337013, we've started wondering about how to handle `wdqs-categories`. Do we... - continue to run it on all hosts? - migrate it to its own environment? -- If we migrate, would it be VMs or Kubernetes? Creating this ticket to discuss why might want to move this service (easier to operate? fewer resources?) , level of effort involved with the status quo vs. migration, etc. If we do decide to migrate, we'll handle the work in a subsequent ticket.