Re: Re: Hot standby problems: consistent state not reached, no connection to master server.

On 04/13/2015 09:42 AM, Ilya Ashchepkov wrote:
> On Sun, 12 Apr 2015 17:30:44 -0700
> Adrian Klaver <adrian.klaver@aklaver.com> wrote:
>

>>>>
>>>
>>> Oh! I missed this! Thank you!
>>> Now slave reached consistent state some time after start, but still
>>> no connection to master server and still restoring wal-files.
>>
>> Not quite sure what you are getting at.
>>
>> You are not seeing the streaming connection happening?
>
> Yes, no streaming connection.
>
>> If a connection is not being made:
>>
>> 1) Dose user replication have REPLICATION rights?
>> 2) Is the pg_hba.conf on the master set up to allow a connection from
>> the standby for user replication and database replication?
>
> I commented 'restore_command' in recovery.conf and after start slave
> connected to master.
> Then I uncomment it back. Is it possible to have a both, streaming
> connection and restoring from wal files from NFS share?

Yes:

http://www.postgresql.org/docs/9.3/interactive/warm-standby.html#STREAMING-REPLICATION

I wonder if your master is recycling WALs fast enough that the streaming
can't find them and the standby has to go to the archive instead.

What is your wal_keep_segments on the master set to?:

http://www.postgresql.org/docs/9.3/interactive/runtime-config-replication.html#RUNTIME-CONFIG-REPLICATION-SENDER

>
>>
>> Where are the WAL files coming from?
>
> NFS share on master.
>
>>
>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>
>


--
Adrian Klaver
adrian.klaver@aklaver.com