honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-25 09:28:27 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add Sysprop to Adjust IO Buffer Size (#48267) (#48667)

Browse Source 
The 1MB IO-buffer size per transport thread is causing trouble in
some tests, albeit at a low rate. Reducing the number of transport
threads was not enough to fully fix this situation.
Allowing to configure the size of the buffer and reducing it by
more than an order of magnitude should fix these tests.

Closes #46803
This commit is contained in:
Yogesh Gaikwad 2019-10-30 14:19:54 +11:00 committed by GitHub
parent 1b64c1992a
commit 9ed7352a12
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
modules/transport-netty4/src/main/java/org/elasticsearch/transport/CopyBytesSocketChannel.java
View File

@ -39,6 +39,7 @@ import io.netty.channel.ChannelOutboundBuffer;
import io.netty.channel.RecvByteBufAllocator;
import io.netty.channel.socket.nio.NioSocketChannel;
import org.elasticsearch.common.SuppressForbidden;
import org.elasticsearch.common.unit.ByteSizeValue;
import java.io.IOException;
import java.nio.ByteBuffer;
@ -60,7 +61,8 @@ import static io.netty.channel.internal.ChannelUtils.MAX_BYTES_PER_GATHERING_WRI
@SuppressForbidden(reason = "Channel#write")
public class CopyBytesSocketChannel extends NioSocketChannel {
private static final int MAX_BYTES_PER_WRITE = 1 << 20;
private static final int MAX_BYTES_PER_WRITE = StrictMath.toIntExact(ByteSizeValue.parseBytesSizeValue(
System.getProperty("es.transport.buffer.size", "1m"), "es.transport.buffer.size").getBytes());
private static final ThreadLocal<ByteBuffer> ioBuffer = ThreadLocal.withInitial(() -> ByteBuffer.allocateDirect(MAX_BYTES_PER_WRITE));
private final WriteConfig writeConfig = new WriteConfig();

6
x-pack/plugin/security/build.gradle
View File

@ -315,6 +315,12 @@ test {
* other if we allow them to set the number of available processors as it's set-once in Netty.
*/
systemProperty 'es.set.netty.runtime.available.processors', 'false'
/*
* Some tests in this module set up a lot of transport threads so we reduce the buffer size per transport thread from the 1M default
* to keep direct memory usage under control.
*/
systemProperty 'es.transport.buffer.size', '256k'
}
// xpack modules are installed in real clusters as the meta plugin, so