[LU-9443] omit changelogs for volatile files Created: 03/May/17 Updated: 09/May/17 Resolved: 09/May/17 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.10.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Minh Diep | Assignee: | Minh Diep |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | changelog, hsm, robinhood | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
The slow rate of changelog consumption is probably the biggest issue for Robinhood deployments. So let's try emit as few changelog records as are necessary. AFAICT we can omit changelogs for volatile files without affecting RBH. As for other changelog consumers, who knows? rsync? Are there others? |
| Comments |
| Comment by Gerrit Updater [ 03/May/17 ] |
|
Minh Diep (minh.diep@intel.com) uploaded a new patch: https://review.whamcloud.com/26931 |
| Comment by Andreas Dilger [ 04/May/17 ] |
|
In theory, it should also be possible to skip records like setattr that only affect timestamp changes, in particular atime, so long as these are not also affecting the data. That may already be done, I'm not sure. |
| Comment by Gerrit Updater [ 09/May/17 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch https://review.whamcloud.com/26931/ |
| Comment by Peter Jones [ 09/May/17 ] |
|
Landed for 2.10 |