2016-10-26 10:13 GMT-02:00 Flavio Henrique Araque Gurgel <fha...@gmail.com>:
> > > Em qua, 26 de out de 2016 às 13:03, Cleiton Luiz Domazak < > cleitondoma...@gmail.com> escreveu: > >> Bom dia. >> >> Ativei o archive e estou utilizando o Wal-e, porém hoje percebi em um dos >> servidores de teste que um range inteiro de Wal files não foram >> processados, eles estão na pg_xlog, e não foram processados pelo >> archive_command e nem estão na archive_status. >> >> Alguém tem alguma idéia do pq? >> > > Você tem que ter algo no log. Assim "a seco", difícil. > Exatamente é esse o meu problema kkkk, não tem nada nos logs. > > >> >> O ambiente é "PostgreSQL 9.4.9 x64 em CentOS 7 x64" >> >> postgresql.conf >> >> checkpoint_segments = 64 >> checkpoint_completion_target = 0.9 >> wal_buffers = 16MB >> default_statistics_target = 100 >> wal_keep_segments = 30 >> max_wal_senders = 3 >> wal_level = hot_standby >> archive_mode = on >> archive_command = 'envdir /etc/wal-e.d/env wal-e wal-push %p' >> archive_timeout = 60 >> >> Uma parte dos arquivos gerados, o e-mail foi escrito 26/10/16 - 08:58: >> >> -rw------- 1 postgres postgres 16777216 Oct 26 07:45 >> 000000010000011B00000027 >> -rw------- 1 postgres postgres 16777216 Oct 26 07:44 >> 000000010000011B00000028 >> -rw------- 1 postgres postgres 16777216 Oct 26 07:46 >> 000000010000011B00000029 >> -rw------- 1 postgres postgres 16777216 Oct 26 07:50 >> 000000010000011B0000002A >> -rw------- 1 postgres postgres 16777216 Oct 26 07:51 >> 000000010000011B0000002B >> -rw------- 1 postgres postgres 16777216 Oct 26 07:52 >> 000000010000011B0000002C >> -rw------- 1 postgres postgres 16777216 Oct 26 07:53 >> 000000010000011B0000002D >> -rw------- 1 postgres postgres 16777216 Oct 26 07:57 >> 000000010000011B0000002E >> -rw------- 1 postgres postgres 16777216 Oct 26 07:54 >> 000000010000011B0000002F >> -rw------- 1 postgres postgres 16777216 Oct 26 07:58 >> 000000010000011B00000030 >> -rw------- 1 postgres postgres 16777216 Oct 26 07:55 >> 000000010000011B00000031 >> -rw------- 1 postgres postgres 16777216 Oct 26 07:56 >> 000000010000011B00000032 >> -rw------- 1 postgres postgres 16777216 Oct 26 07:59 >> 000000010000011B00000033 >> -rw------- 1 postgres postgres 16777216 Oct 26 08:05 >> 000000010000011B00000034 >> -rw------- 1 postgres postgres 16777216 Oct 26 08:04 >> 000000010000011B00000035 >> -rw------- 1 postgres postgres 16777216 Oct 26 08:02 >> 000000010000011B00000036 >> -rw------- 1 postgres postgres 16777216 Oct 26 08:03 >> 000000010000011B00000037 >> -rw------- 1 postgres postgres 16777216 Oct 26 08:00 >> 000000010000011B00000038 >> -rw------- 1 postgres postgres 16777216 Oct 26 08:01 >> 000000010000011B00000039 >> -rw------- 1 postgres postgres 16777216 Oct 26 08:06 >> 000000010000011B0000003A >> -rw------- 1 postgres postgres 16777216 Oct 26 08:07 >> 000000010000011B0000003B >> -rw------- 1 postgres postgres 16777216 Oct 26 08:09 >> 000000010000011B0000003C >> -rw------- 1 postgres postgres 16777216 Oct 26 08:08 >> 000000010000011B0000003D >> >> >> Conteúdo da archive_status: >> >> -rw------- 1 postgres postgres 0 Oct 25 21:23 00000001000001170000005C. >> 00000028.backup.done >> -rw------- 1 postgres postgres 0 Oct 26 08:25 >> 000000010000011A000000CB.done >> -rw------- 1 postgres postgres 0 Oct 26 08:26 >> 000000010000011A000000CC.done >> -rw------- 1 postgres postgres 0 Oct 26 08:27 >> 000000010000011A000000CD.done >> -rw------- 1 postgres postgres 0 Oct 26 08:28 >> 000000010000011A000000CE.done >> -rw------- 1 postgres postgres 0 Oct 26 08:29 >> 000000010000011A000000CF.done >> -rw------- 1 postgres postgres 0 Oct 26 08:30 >> 000000010000011A000000D0.done >> -rw------- 1 postgres postgres 0 Oct 26 08:31 >> 000000010000011A000000D1.done >> -rw------- 1 postgres postgres 0 Oct 26 08:32 >> 000000010000011A000000D2.done >> -rw------- 1 postgres postgres 0 Oct 26 08:33 >> 000000010000011A000000D3.done >> -rw------- 1 postgres postgres 0 Oct 26 08:34 >> 000000010000011A000000D4.done >> -rw------- 1 postgres postgres 0 Oct 26 08:35 >> 000000010000011A000000D5.done >> -rw------- 1 postgres postgres 0 Oct 26 08:36 >> 000000010000011A000000D6.done >> -rw------- 1 postgres postgres 0 Oct 26 08:37 >> 000000010000011A000000D7.done >> -rw------- 1 postgres postgres 0 Oct 26 08:38 >> 000000010000011A000000D8.done >> -rw------- 1 postgres postgres 0 Oct 26 08:39 >> 000000010000011A000000D9.done >> -rw------- 1 postgres postgres 0 Oct 26 08:40 >> 000000010000011A000000DA.done >> -rw------- 1 postgres postgres 0 Oct 26 08:41 >> 000000010000011A000000DB.done >> -rw------- 1 postgres postgres 0 Oct 26 08:42 >> 000000010000011A000000DC.done >> -rw------- 1 postgres postgres 0 Oct 26 08:43 >> 000000010000011A000000DD.done >> -rw------- 1 postgres postgres 0 Oct 26 08:44 >> 000000010000011A000000DE.done >> -rw------- 1 postgres postgres 0 Oct 26 08:45 >> 000000010000011A000000DF.done >> -rw------- 1 postgres postgres 0 Oct 26 08:46 >> 000000010000011A000000E0.done >> -rw------- 1 postgres postgres 0 Oct 26 08:47 >> 000000010000011A000000E1.done >> -rw------- 1 postgres postgres 0 Oct 26 08:48 >> 000000010000011A000000E2.done >> -rw------- 1 postgres postgres 0 Oct 26 08:49 >> 000000010000011A000000E3.done >> -rw------- 1 postgres postgres 0 Oct 26 08:50 >> 000000010000011A000000E4.done >> -rw------- 1 postgres postgres 0 Oct 26 08:51 >> 000000010000011A000000E5.done >> -rw------- 1 postgres postgres 0 Oct 26 08:52 >> 000000010000011A000000E6.done >> -rw------- 1 postgres postgres 0 Oct 26 08:53 >> 000000010000011A000000E7.done >> -rw------- 1 postgres postgres 0 Oct 26 08:54 >> 000000010000011A000000E8.done >> -rw------- 1 postgres postgres 0 Oct 26 08:55 >> 000000010000011A000000E9.done >> -rw------- 1 postgres postgres 0 Oct 26 08:56 >> 000000010000011A000000EA.done >> -rw------- 1 postgres postgres 0 Oct 26 08:57 >> 000000010000011A000000EB.done >> >> >> Nos logs do PostgreSQL não existe nenhuma referencia para os arquivos que >> não foram processados, nem com erro do arquivamento feito pelo Wal-e. >> > > Então ele arquivou. > Você olhou no seu bucket S3 se os arquivos não estão lá? > O PostgreSQL não remove imediatamente os arquivos após arquivamento, ele > vai renomeá-los depois para os novos segmentos necessários. > Estou ciente disso, fiz uma checagem full dos arquivos do bucket, e os que faltam é justamente esse range, e ele não está sendo apagado da pg_xlog até pq não foi archivado ainda. > > >> >> >> Na pg_stat_archiver também não tem nenhuma referencia de erro. >> >> É como simplesmente esses arquivos não existissem. >> > > O que quer dizer com "não existissem"? Eles não cairam no seu bucket? > Sim, nem no bucket e nem no archive_status, é como eles tivessem sido criados pelo banco, mas não existissem para o archive_command > > []s > Flavio Gurgel > > _______________________________________________ > pgbr-geral mailing list > pgbr-geral@listas.postgresql.org.br > https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral >
_______________________________________________ pgbr-geral mailing list pgbr-geral@listas.postgresql.org.br https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
