Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-13269

Mesh: Migration of LFS objects to Mesh



    • Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • None
    • Mesh
    • None
    • 0
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.



      Migrating Git repositories to Mesh before migration of LFS objects is implemented is very much possible and supported. The LFS object will continue to reside on the NFS based shared home and can be migrated later.

      Generally lack of LFS migration doesn't need to be seen as a blocker to adopting Mesh. Core Git I/O patterns often involve small and semi-random I/O, which suffers due the additional latency involved in accessing files via NFS, this isn't so true of LFS objects. Git LFS object read I/O is involves large block and sequential read patters, and generally don't suffer heavily from being hosted on NFS.

      The initial (Bitbucket 8.0) release of Mesh does not include functionality for migrating LFS objects to Mesh. Git LFS continues to be supported when Git repositories are migrated to Mesh; the LFS object will simply remain in the shared-home (i.e. the NFS when in a cluster deployment).


        Issue Links



              Unassigned Unassigned
              behumphreys Ben Humphreys
              14 Vote for this issue
              14 Start watching this issue