Xavi Hernandez

We have checked this in the slack channel and the problem is that the I/O framework introduced in release 10 uses real 64 bit atomic variables. In 32 bits architectures...

We decided to not support 32 bits (i.e. no testing is done) but we do keep compiling it to make sure that at least compiles and should work. The problem...

In this particular case it's necessary to change how things are implemented. It's not just a build configuration. Just changing the value to 32 bits is not enough because it...

Thanks @kevinpawsey. I'll take it into account when something needs to be tested in 32 bits architectures

@amarts @pranithk @mohit84 what do you think ? I would say that we could just remove open-behind, but at least we need to disable it by default.

> the open file descriptor usecase is very common. What's this common use case ? anything that requires almost any other operation after open, won't avoid the open, so the...

> > @amarts @pranithk @mohit84 what do you think ? > > I would say that we could just remove open-behind, but at least we need to disable it by...

> the open file descriptor usecase is very common. My take is, we should disable open-behind by default (Actually I thought its disabled by default already). Now that I re-read...

> We are seeing regression for read fop > > ``` > read 29017 19692 -32 > ``` This is with 64 KiB files, right ? can it be tested...

/recheck smoke