Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add more translog details to recovery API output #9368

Closed
ppf2 opened this issue Jan 20, 2015 · 3 comments
Closed

Add more translog details to recovery API output #9368

ppf2 opened this issue Jan 20, 2015 · 3 comments
Labels
:Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement help wanted adoptme

Comments

@ppf2
Copy link
Member

ppf2 commented Jan 20, 2015

We have seen recovery processes appearing to be stuck in translog state (or taking a very long time to recover) on various occasions. The recovery API currently shows how much it has recovered and the total_time spent recovering:

      "translog" : {
        "recovered" : 7308178,
        "total_time" : "0s",
        "total_time_in_millis" : 0
      }

It will be helpful to also show (similar the recovery output for index files):

  • The size of the translog that is being recovered
  • % recovered so far
  • Elasped time specific to the translog recovery operation
@clintongormley
Copy link

+1

@clintongormley clintongormley added help wanted adoptme :Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement labels Jan 20, 2015
@bleskes
Copy link
Contributor

bleskes commented Jan 20, 2015

while we at it, can we also increment the total_time as we go along? right now it's only update at the end. Also, it seems it is only updated on recovery from gateway , not peer recovery.

@mikemccand
Copy link
Contributor

+1

bleskes added a commit to bleskes/elasticsearch that referenced this issue Mar 9, 2015
@bleskes
Recovery: add total operations to the _recovery API
ebbd35c 
This commit adds the current total number of translog operations to the recovery reporting API.  We also expose the recovered / total percentage:

```
"translog": {
     "recovered": 536,
     "total": 986,
     "percent": "54.3%",
     "total_time": "2ms",
     "total_time_in_millis": 2
},
```

Closes elastic#9368
@bleskes bleskes mentioned this issue Mar 9, 2015
Closed
bleskes added a commit that referenced this issue Mar 17, 2015
@bleskes
Recovery: add total operations to the _recovery API
c028c4e 
This commit adds the current total number of translog operations to the recovery reporting API.  We also expose the recovered / total percentage:

```
"translog": {
     "recovered": 536,
     "total": 986,
     "percent": "54.3%",
     "total_time": "2ms",
     "total_time_in_millis": 2
},
```

Closes #9368
Closes #10042
bleskes added a commit that referenced this issue Mar 17, 2015
@bleskes
Recovery: add total operations to the _recovery API
6e8a9c1 
This commit adds the current total number of translog operations to the recovery reporting API.  We also expose the recovered / total percentage:

```
"translog": {
     "recovered": 536,
     "total": 986,
     "percent": "54.3%",
     "total_time": "2ms",
     "total_time_in_millis": 2
},
```

Closes #9368
Closes #10042
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
@bleskes
Recovery: add total operations to the _recovery API
17e42e3 
This commit adds the current total number of translog operations to the recovery reporting API.  We also expose the recovered / total percentage:

```
"translog": {
     "recovered": 536,
     "total": 986,
     "percent": "54.3%",
     "total_time": "2ms",
     "total_time_in_millis": 2
},
```

Closes elastic#9368
Closes elastic#10042
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed/Recovery Anything around constructing a new shard, either from a local or a remote source. >enhancement help wanted adoptme
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@clintongormley @mikemccand @bleskes @ppf2