You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@hawq.apache.org by mailing-list-recv <ma...@sequoiadb.com> on 2015/10/29 05:24:23 UTC

only master able to accept incoming connections?

From the architecture’s perspective, there seems only a single master ( and a standby ) is able to receive incoming connections.

So if the number of incoming applications keep increasing, a single master could become the bottleneck.




Right now master seems responsible for handling both catalog and incoming connections, is there any plan to separate the responsibilities to multiple processes in the future?




Cheers

Re: only master able to accept incoming connections?

Posted by Lei Chang <ch...@gmail.com>.

Actually, from real user applications, we rarely encounter master
bottleneck since the main work is on segments.

The future plan is to have multiple masters.

Cheers
Lei


On Thu, Oct 29, 2015 at 12:24 PM, mailing-list-recv <
mailing-list-recv@sequoiadb.com> wrote:

> From the architecture’s perspective, there seems only a single master (
> and a standby ) is able to receive incoming connections.
>
> So if the number of incoming applications keep increasing, a single master
> could become the bottleneck.
>
>
> Right now master seems responsible for handling both catalog and incoming
> connections, is there any plan to separate the responsibilities to multiple
> processes in the future?
>
>
> Cheers
>