[LU-7079] OSP shouldn't discard requests due to imp_peer_committed_transno Created: 01/Sep/15 Updated: 30/Jan/17 Resolved: 07/Sep/15 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.8.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Alex Zhuravlev | Assignee: | Alex Zhuravlev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Severity: | 3 | ||||||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||||||
| Description |
|
imp_peer_committed_transno isn't always actual. this leads to confusing sequence when req's commit_cb() is called, but imp_peer_committed_transno claims the request hasn't been committed yet. in this case we shouldn't release request, instead we have to put it back on opd_syn_committed_there list and wait till imp_peer_committed_transno is updated. |
| Comments |
| Comment by Gerrit Updater [ 04/Sep/15 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/16161/ |
| Comment by Peter Jones [ 07/Sep/15 ] |
|
Landed for 2.8 |