We are using clustering to share configuration settings in environments that do load balancing across multiple proxies. Administrators that have large deployments would need to configure every proxy manually.
-Hai From: Bryan Call [mailto:bc...@apache.org] Sent: Monday, August 29, 2016 3:52 PM To: Nguyen, Hai Cc: d...@trafficserver.apache.org; users@trafficserver.apache.org Subject: EXTERNAL: Re: Re: [PROPOSAL] Removing clustering support in 7.0.0 Can you talk about how you are using the clustering feature? Would parent proxying also work for your use case? -Bryan On Aug 29, 2016, at 3:30 PM, Nguyen, Hai <hngu...@forcepoint.com<mailto:hngu...@forcepoint.com>> wrote: I’m sorry for sending the feedback on this proposal late. Can we please keep the clustering feature? We’ve been using it extensively here. Thanks, -Hai From: Bryan Call [mailto:bc...@apache.org] Sent: Monday, August 29, 2016 3:20 PM To: d...@trafficserver.apache.org<mailto:d...@trafficserver.apache.org> Cc: users@trafficserver.apache.org<mailto:users@trafficserver.apache.org> Subject: EXTERNAL: Re: [PROPOSAL] Removing clustering support in 7.0.0 Thank you for all the feedback on this proposal. Removing clustering support will be done in 7.0.0. -Bryan On Aug 20, 2016, at 6:33 PM, Leif Hedstrom <zw...@apache.org<mailto:zw...@apache.org>> wrote: On Aug 19, 2016, at 3:18 PM, James Peach <jpe...@apache.org<mailto:jpe...@apache.org>> wrote: On Aug 19, 2016, at 11:08 AM, Bryan Call <bc...@apache.org<mailto:bc...@apache.org>> wrote: There are a few features we are looking to remove in the ATS 7.0.0 release. If you are using these features and require them, please respond to this email. We also need to have people that are willing to invest time and fix some of the bugs for these features. Your feedback is very important! There are a number of bugs filed against clustering. There are alternatives to using clustering, such as parent selection and the CARP plugin that Yahoo is open sourcing. If we are going to keep clustering supporting we would need someone that is willing to work on the bugs. The proposal is to remove the configurations options for clustering and remove the code for it. I've seen a few people asking about clustering recently, so it seems like there is interest. But it *really* needs a code owner to make it live. Count me as a +0. A serious issue with the lack of developer support is that other areas of the code suffers. Meaning, we have a hard time making progress with other areas (like metrics, or configurations), because we don’t have anyone who’s testing and maintaining the clustering feature. This is a tough one though, the general feature is useful, but we’re seriously crippling ourselves with an unsupported legacy system. +0 from me as well. — Leif Scanned by Forcepoint Email Security Gateway Click here<https://esgpem.websense.com/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5e05ab970ae3ca9cc1d4d703e3a16bba58faf015599e14c7422c0fe0e50f83ec29c6a066df750951d586cbd4b9c445f9f7ede47b5ff2432e6db5d9ab138ccf9f92096d50fce4041f5c685b71e990171ff43cba7313b924b534e998c2f8842e648735033d6e98ce3c50b6ef6e38032c0f11163d221beb5819204db1eb665a0f03fd0ef0444d79aef489> to report this email as spam Scanned by Forcepoint Email Security Gateway Click here<https://esgpem.websense.com:443/pem/pages/digestProcess/digestProcess.jsf?content=c3805c5951889c5eac36c03d0e7ff0b57b7e3ed898c04d3b57443d4dd6633da2a02f7e00cad8ee51e76369bb7724613990fab7f6a77e81c146894a278e2586fe25ecf0e847b3e8c92d9fea959c461e1b4b8eadc7dda39f476525df499317859b67ad36e597e46f717050f777046e98b211aa34ec38cc86034854bfa41cee96304774a1766865ea10> to report this email as spam
