[Bugs] [Bug 1512691] PostgreSQL DB Restore: unexpected data beyond EOF

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1512691

Philip Chan <chanphil at us.ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |chanphil at us.ibm.com



--- Comment #8 from Philip Chan <chanphil at us.ibm.com> ---
(In reply to Milo from comment #1)
> Same problem here. I read that most databases are not supported on Gluster
> but could we fix that?
> See "Gluster does not support so called “structured data”, meaning live, SQL
> databases." in http://docs.gluster.org/en/latest/Install-Guide/Overview/.
> 
> We are running:
> - glusterfs 3.12.3
> - kernel 3.10.0-693.el7.x86_64
> - Red Hat Enterprise Linux Server release 7.4 (Maipo)
> 
> It seems to be a problem with lseek(SEEK_END) not taking into account the
> last write in hi-traffic situations.
> See postgres source code in "src/backend/storage/buffer/bufmgr.c" around
> line 806.

We have also hit the same problem under heavy load when populating ou database
inside a Postgresql container mapped to a Replicated Glusterfs volume.  Our
environment consists of:
- glusterfs 3.12.3
- kernel 4.4.0-31-generic
- Ubuntu Ubuntu 16.04.3 LTS

We applied the workaround as mentioned in Bug#1518710 (turning off both
performance.open-behind and performance.write-behind) that helped rid the load
errors.

My questions are:
1) Can RedHat please clarify the statement "Gluster does not support so called
“structured data”, meaning live, SQL databases." means? Is this to say the
configuration we have(postgres using a glusterfs volume) is not supported?
2) What exact version of Gluster is this problem targeted to be fixed? About
what time frame?

Thanks,
-Phil

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=IY7pKQ0tVg&a=cc_unsubscribe