infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-13384) Tidy up Database Servers (Names and Services)
Date Wed, 23 Aug 2017 02:32:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-13384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus resolved INFRA-13384.
-------------------------------------
    Resolution: Workaround

After dealing with some weird performance issues, I've decided that co-hosting DBs on the
same box is a bad idea. We can afford the extra IPs and resources because it reduces admin
headaches and stress. The naming can be addressed through attrition since we need to upgrade
many of the existing boxes to 16.04. 


> Tidy up Database Servers (Names and Services)
> ---------------------------------------------
>
>                 Key: INFRA-13384
>                 URL: https://issues.apache.org/jira/browse/INFRA-13384
>             Project: Infrastructure
>          Issue Type: Epic
>          Components: Puppet
>            Reporter: Daniel Gruno
>            Assignee: Chris Lambertus
>   Original Estimate: 1,344h
>  Remaining Estimate: 1,344h
>
> The database layout we currently have seems inefficient and confusing.
> Some changes are needed, suggestions are:
> - Name all DB instances after their DC location instead of north/south/etc.
> - Pool services (pgsql+mysql+ES) on a single box to save on resources and IPs. Just call
them database-$dc-$subdc.apache.org or such.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message