# Transactions logs stored at the wrong place

**URL:** <https://discuss.elastic.co/t/transactions-logs-stored-at-the-wrong-place/22410>\
**Category:** Elasticsearch\
**Created:** [February 26, 2015, 2:58pm UTC](https://discuss.elastic.co/t/transactions-logs-stored-at-the-wrong-place/22410 "2015-02-26T14:58:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Herve\_Bry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/herve_bry/32/12706_2.png) [@Herve\_Bry](https://discuss.elastic.co/u/Herve_Bry)\
**Post date:** [February 26, 2015, 2:58pm UTC](https://discuss.elastic.co/t/transactions-logs-stored-at-the-wrong-place/22410/1 "2015-02-26T14:58:53Z")

</div>

Hello Community,

I noticed a strange behavior while setting up my ES 1.4.4 cluster: the  
transactions logs seem to be stored at the wrong place.

I start ES using the option --default.path.data=/var/lib/elasticsearch  
(default setting when using deb packages).  
Then, in /etc/elasticsearch/elasticsearch.yml, I change the data path for 4  
SSD :

path.data:  
- /data/self/1  
- /data/self/2  
- /data/self/3  
- /data/self/4

When I create an index and start pushing data, the shards are correctly  
created on my SSD  
(/data/self/_/clustername/nodes/0/indices/indexname/_/index/_) but the  
transaction logs are created in  
/var/lib/elasticsearch/clustername/nodes/0/indices/indexname/_/translog/translog-\*.

It seems like the config file did correctly override the data path setting  
for the shards but not for the transactions logs.

Did I miss something or is it a bug ?

Regards,

Hervé BRY  
System Administrator  
www.geneanet.org

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [March 1, 2015, 8:14am UTC](https://discuss.elastic.co/t/transactions-logs-stored-at-the-wrong-place/22410/2 "2015-03-01T08:14:41Z")

</div>

Well the translog isn't really data like an index is, however you raise a  
valid point if this is the behaviour.

Is it a problem for you to have them there or just a point of interest?

On 27 February 2015 at 01:58, Hervé Bry [herve.bry@geneanet.org](mailto:herve.bry@geneanet.org) wrote:

> Hello Community,
> 
> I noticed a strange behavior while setting up my ES 1.4.4 cluster: the  
> transactions logs seem to be stored at the wrong place.
> 
> I start ES using the option --default.path.data=/var/lib/elasticsearch  
> (default setting when using deb packages).  
> Then, in /etc/elasticsearch/elasticsearch.yml, I change the data path for  
> 4 SSD :
> 
> path.data:  
> - /data/self/1  
> - /data/self/2  
> - /data/self/3  
> - /data/self/4
> 
> When I create an index and start pushing data, the shards are correctly  
> created on my SSD  
> (/data/self/_/clustername/nodes/0/indices/indexname/_/index/_) but the  
> transaction logs are created in  
> /var/lib/elasticsearch/clustername/nodes/0/indices/indexname/_/translog/translog-\*.
> 
> It seems like the config file did correctly override the data path setting  
> for the shards but not for the transactions logs.
> 
> Did I miss something or is it a bug ?
> 
> Regards,
> 
> Hervé BRY  
> System Administrator  
> [www.geneanet.org](http://www.geneanet.org)
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9%3DFTtgUULodnm\_OVSJDDY%3D%3Dqpgio%3DALQ618hv830gY%3DA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9%3DFTtgUULodnm_OVSJDDY%3D%3Dqpgio%3DALQ618hv830gY%3DA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Herve\_Bry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/herve_bry/32/12706_2.png) [@Herve\_Bry](https://discuss.elastic.co/u/Herve_Bry)\
**Post date:** [March 2, 2015, 10:10am UTC](https://discuss.elastic.co/t/transactions-logs-stored-at-the-wrong-place/22410/3 "2015-03-02T10:10:13Z")

</div>

Well, my /var/lib partition is small while I have 4 SSD with plenty of  
space that I use to store indices.  
So I have ran several times into a "no more space on device" situation when  
a developer decided to increase index.translog.flush\_threshold\_size to  
speed up indexing. And then I could not even flush the index because there  
was not enough space to create new empty translogs.

I managed to move the translogs to the path.data configured in  
elasticsearch.yml by removing the --default.path.data option from the init  
script. However this is not a good solution as it involves altering a  
packaged file.

It would be nice to either store translogs correctly with the corresponding  
indices or have a setting to change the storage path.

Regards,

Hervé BRY  
System Administrator

> **[Geneanet - Réinventons la Généalogie](https://www.geneanet.org/)**
>
> Créez votre arbre généalogique. Ecrivez et partagez votre histoire familiale sur Geneanet.

Le dimanche 1 mars 2015 09:15:08 UTC+1, Mark Walkom a écrit :

> Well the translog isn't really data like an index is, however you raise a  
> valid point if this is the behaviour.
> 
> Is it a problem for you to have them there or just a point of interest?
> 
> On 27 February 2015 at 01:58, Hervé Bry \<[herv...@geneanet.org](mailto:herv...@geneanet.org)  
> \<javascript:\>\> wrote:
> 
> > Hello Community,
> > 
> > I noticed a strange behavior while setting up my ES 1.4.4 cluster: the  
> > transactions logs seem to be stored at the wrong place.
> > 
> > I start ES using the option --default.path.data=/var/lib/elasticsearch  
> > (default setting when using deb packages).  
> > Then, in /etc/elasticsearch/elasticsearch.yml, I change the data path for  
> > 4 SSD :
> > 
> > path.data:  
> > - /data/self/1  
> > - /data/self/2  
> > - /data/self/3  
> > - /data/self/4
> > 
> > When I create an index and start pushing data, the shards are correctly  
> > created on my SSD  
> > (/data/self/_/clustername/nodes/0/indices/indexname/_/index/_) but the  
> > transaction logs are created in  
> > /var/lib/elasticsearch/clustername/nodes/0/indices/indexname/_/translog/translog-\*.
> > 
> > It seems like the config file did correctly override the data path  
> > setting for the shards but not for the transactions logs.
> > 
> > Did I miss something or is it a bug ?
> > 
> > Regards,
> > 
> > Hervé BRY  
> > System Administrator  
> > [www.geneanet.org](http://www.geneanet.org)
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/285ac8c0-b0bd-4885-943c-e088a5989673%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/285ac8c0-b0bd-4885-943c-e088a5989673%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [March 2, 2015, 11:04am UTC](https://discuss.elastic.co/t/transactions-logs-stored-at-the-wrong-place/22410/4 "2015-03-02T11:04:36Z")

</div>

Understood! You should definitely raise this as an issue on Github -

> **[Issues · elastic/elasticsearch](https://github.com/elastic/elasticsearch/issues)**
>
> Free and Open, Distributed, RESTful Search Engine. Contribute to elastic/elasticsearch development by creating an account on GitHub.

On 2 March 2015 at 21:10, Hervé Bry [herve.bry@geneanet.org](mailto:herve.bry@geneanet.org) wrote:

> Well, my /var/lib partition is small while I have 4 SSD with plenty of  
> space that I use to store indices.  
> So I have ran several times into a "no more space on device" situation  
> when a developer decided to increase index.translog.flush\_threshold\_size to  
> speed up indexing. And then I could not even flush the index because there  
> was not enough space to create new empty translogs.
> 
> I managed to move the translogs to the path.data configured in  
> elasticsearch.yml by removing the --default.path.data option from the init  
> script. However this is not a good solution as it involves altering a  
> packaged file.
> 
> It would be nice to either store translogs correctly with the  
> corresponding indices or have a setting to change the storage path.
> 
> Regards,
> 
> Hervé BRY  
> System Administrator  
> [www.geneanet.org](http://www.geneanet.org)
> 
> Le dimanche 1 mars 2015 09:15:08 UTC+1, Mark Walkom a écrit :
> 
> > Well the translog isn't really data like an index is, however you raise a  
> > valid point if this is the behaviour.
> > 
> > Is it a problem for you to have them there or just a point of interest?
> > 
> > On 27 February 2015 at 01:58, Hervé Bry [herv...@geneanet.org](mailto:herv...@geneanet.org) wrote:
> > 
> > > Hello Community,
> > > 
> > > I noticed a strange behavior while setting up my ES 1.4.4 cluster: the  
> > > transactions logs seem to be stored at the wrong place.
> > > 
> > > I start ES using the option --default.path.data=/var/lib/elasticsearch  
> > > (default setting when using deb packages).  
> > > Then, in /etc/elasticsearch/elasticsearch.yml, I change the data path  
> > > for 4 SSD :
> > > 
> > > path.data:  
> > > - /data/self/1  
> > > - /data/self/2  
> > > - /data/self/3  
> > > - /data/self/4
> > > 
> > > When I create an index and start pushing data, the shards are correctly  
> > > created on my SSD (/data/self/_/clustername/nodes/0/indices/indexname/_/index/_)  
> > > but the transaction logs are created in /var/lib/elasticsearch/  
> > > clustername/nodes/0/indices/indexname/_/translog/translog-\*.
> > > 
> > > It seems like the config file did correctly override the data path  
> > > setting for the shards but not for the transactions logs.
> > > 
> > > Did I miss something or is it a bug ?
> > > 
> > > Regards,
> > > 
> > > Hervé BRY  
> > > System Administrator  
> > > [www.geneanet.org](http://www.geneanet.org)
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/)  
> > > msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%  
> > > [40googlegroups.com](http://40googlegroups.com)  
> > > [https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/72e5ff83-c4e0-42c5-b3ff-2dd3ef41b352%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > > .  
> > > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/285ac8c0-b0bd-4885-943c-e088a5989673%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/285ac8c0-b0bd-4885-943c-e088a5989673%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/285ac8c0-b0bd-4885-943c-e088a5989673%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/285ac8c0-b0bd-4885-943c-e088a5989673%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-0dFvCO1nyJupJ25avLXC\_bbPwT\_LNMZtFoNqzPfU%3DzA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-0dFvCO1nyJupJ25avLXC_bbPwT_LNMZtFoNqzPfU%3DzA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:29am UTC](https://discuss.elastic.co/t/transactions-logs-stored-at-the-wrong-place/22410/5 "2017-07-06T00:29:06Z")

</div>


