0.13.0: work and data dirs

Elastic Stack Elasticsearch
1

Hi,

I'm unsure about the usage of the "work" directory in the newest
0.13.0 release. I don't get a "work" directory at my installation
(since I don't run a cluster?). But it's my understanding that it is
still being used.
Should I point "path.work" to the same directory as "path.data"? Or
rather to /tmp? What's stored in it?

Sincerely,
Reto

2

Hi,

Currently, nothing is stored in path.work, but in the future temporary
data might be stored there. So, the best place for it is a local temp
location.

-shay.banon

On Mon, Nov 29, 2010 at 9:49 PM, Reto retoonline@gmail.com wrote:

Hi,

I'm unsure about the usage of the "work" directory in the newest
0.13.0 release. I don't get a "work" directory at my installation
(since I don't run a cluster?). But it's my understanding that it is
still being used.
Should I point "path.work" to the same directory as "path.data"? Or
rather to /tmp? What's stored in it?

Sincerely,
Reto

3

Hey,

Ok, thanks very much - upgrading worked :slight_smile:

Sincerely
Reto

On Nov 29, 10:19 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Hi,

Currently, nothing is stored in path.work, but in the future temporary
data might be stored there. So, the best place for it is a local temp
location.

-shay.banon

On Mon, Nov 29, 2010 at 9:49 PM, Reto retoonl...@gmail.com wrote:

Hi,

I'm unsure about the usage of the "work" directory in the newest
0.13.0 release. I don't get a "work" directory at my installation
(since I don't run a cluster?). But it's my understanding that it is
still being used.
Should I point "path.work" to the same directory as "path.data"? Or
rather to /tmp? What's stored in it?

Sincerely,
Reto