Interface write data cannot be found immediately

__Steps to reproduce:__

summary:The data indicator is to generate a record every hour, and the corresponding record cannot be found immediately after writing the data.
1. After writing data through rest api /api/v2/create?bucket={1}&org={2}&precision=ns, the relevant records cannot be found in GUI explorer.
2. It takes about 30 minutes to find the corresponding records. The default configuration file is used

__Expected behavior:__
I suspect that there is a default write strategy, and I did not find the corresponding parameters in the configuration options

__Actual behavior:__
I can manually configure the merge cache or set a number of merge parameters or time interval

__Environment info:__

* System info: Linux 3.10.0-1127.19.1.el7.x86_64 x86_64
* InfluxDB version: InfluxDB 2.0.1 (git: 37cc047133) build_date: 2020-11-11T03:53:31Z
* Other relevant environment details: default configure

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.

__Logs:__
Include snippet of errors in log.

__Performance:__
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.

```sh
# Commands should be run when the bug is actively happening.
# Note: This command will run for at least 30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=true"
curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz`, `vars.txt`, and `iostat.txt` output files.
```

Start by reproducing the delay through the /api/v2/create REST endpoint with the default configuration, then check when the written data becomes visible in GUI Explorer. Compare the observed behavior with the expected immediate availability and determine whether the default merge-cache behavior or a configurable interval is responsible.

Written by the indexing model from the issue text.