[LU-6244] Handle multiple transactions produced by single request Created: 13/Feb/15 Updated: 16/Jan/22 Resolved: 16/Jan/22 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Mikhail Pershin | Assignee: | Mikhail Pershin |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Severity: | 3 | ||||||||||||
| Rank (Obsolete): | 17485 | ||||||||||||
| Description |
|
Lustre recovery model rely on the fact that each request produces single transaction, meanwhile there can be multiple transactions in single requests by design or by mistakes in design. There is message about in tgt_txn_stop_cb() but it has D_HA level and contains almost no information. I propose to increase level to D_WARNING and put more debugging info to find out what request produce that and execution context. With more new features we start seeing such situations with multiple transaction more often, this change will help to see problem at early stage in developing and handle it properly |
| Comments |
| Comment by Mikhail Pershin [ 13/Feb/15 ] |
|
That would be good to propose some common way how to handle multiple transactions in single requests at all. The need to send a series of updates in single RPC is obvious and will be required more and more. If any changes in protocol are needed, then better to introduce them in advance. |