# ElasticSearch using Docker and BitBucket DataCenter

**URL:** <https://discuss.elastic.co/t/elasticsearch-using-docker-and-bitbucket-datacenter/302163>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [April 11, 2022, 11:39pm UTC](https://discuss.elastic.co/t/elasticsearch-using-docker-and-bitbucket-datacenter/302163 "2022-04-11T23:39:25Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ibmsorerer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ibmsorerer/32/104261_2.png) [@ibmsorerer](https://discuss.elastic.co/u/ibmsorerer)\
**Post date:** [April 11, 2022, 11:39pm UTC](https://discuss.elastic.co/t/elasticsearch-using-docker-and-bitbucket-datacenter/302163/1 "2022-04-11T23:39:25Z")

</div>

We were running BitBucket v6.10.3 as a monolithic server, which has reached EOL.

I've been migrating this system to BB v7.21.0 (current release).  
I've been able to create an ES cluster under Docker/OpenShift without real issue.

After getting ES setup to use 7.16.2 for compatibility with BitBucket, ES only returns 10,000 files unlike what ES did for the earlier version of BitBucket which returned about 6.5 Million files.

Besides this discussion [Pulling more than 10000 records from elasticsearch query](https://discuss.elastic.co/t/pulling-more-than-10000-records-from-elasticsearch-query/181000).

Are there any additional Elasticsearch parameters that will need to be tweaked in order to go back to or emulate the earlier behavior of ES?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 12, 2022, 12:30am UTC](https://discuss.elastic.co/t/elasticsearch-using-docker-and-bitbucket-datacenter/302163/2 "2022-04-12T00:30:26Z")

</div>

Welcome to our community! 😃

That default limit of Elasticsearch has been around for quite some time, and it's always been configurable from the client side. It sounds to me like Bitbucket was doing something that might have changed?

---

<div class="post-metadata">

**Author:** ![ibmsorerer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ibmsorerer/32/104261_2.png) [@ibmsorerer](https://discuss.elastic.co/u/ibmsorerer)\
**Post date:** [April 12, 2022, 1:15am UTC](https://discuss.elastic.co/t/elasticsearch-using-docker-and-bitbucket-datacenter/302163/3 "2022-04-12T01:15:05Z")

</div>

Means that I will need to dig through those config files to increase the limit in the docker version once I find it in the original server.

---

<div class="post-metadata">

**Author:** ![ibmsorerer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ibmsorerer/32/104261_2.png) [@ibmsorerer](https://discuss.elastic.co/u/ibmsorerer)\
**Post date:** [April 13, 2022, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-using-docker-and-bitbucket-datacenter/302163/4 "2022-04-13T20:21:34Z")

</div>

What file contains those settings so that I can set them similarly in the newer variants of Elasticsearch.  
I didn't setup the original server and don't know how they were set/changed.  
I've not tried to read those settings via the API, can I get all of the settings at one time or do I need to query individually?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 11, 2022, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-using-docker-and-bitbucket-datacenter/302163/5 "2022-05-11T20:21:48Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.