[SERVER-49] make admin page have current op? Created: 12/May/09 Updated: 12/Jul/16 Resolved: 26/May/09 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 0.9.3 |
| Fix Version/s: | 0.9.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Eliot Horowitz (Inactive) | Assignee: | Aaron Staple |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
might be nice to have the current op there |
| Comments |
| Comment by Aaron Staple [ 13/May/09 ] |
|
Ok, I just added current op as recorded by existing code to the http interface and placed it's authentication check after the code which generates a report of mongod's current status. Tracking multiple current ops correctly was too much work. |
| Comment by Eliot Horowitz (Inactive) [ 12/May/09 ] |
|
that sounds good. |
| Comment by Aaron Staple [ 12/May/09 ] |
|
Ok, so should we have a current external op and a current internal op? |
| Comment by Eliot Horowitz (Inactive) [ 12/May/09 ] |
|
Not sure - if something inside a db.eval is slow - you kind of want to know both. |
| Comment by Aaron Staple [ 12/May/09 ] |
|
This would be very straightforward, except that the db web server uses a db direct client to authenticate the http login and this resets the recorded currentOp. One option would be to not set currentOp on db direct client requests, which in any case seems like desired behavior in general. Sound ok? |