JGitInternalException: Exception caught during execution of reset command. Cannot lock /data/git-storage/628e37967901344...
Sentry Issue: APPSMITH-1SC
LockFailedException: Cannot lock /data/git-storage/628e37967901344ba8d296e3/629f4d18360bee1cd628fe46/suzuya-studio-rental/.git/index. Ensure that no other process has an open file handle on the lock file /data/git-storage/628e37967901344ba8d296e3/629f4d18360bee1cd628fe46/suzuya-studio-rental/.git/index.lock, then you may delete the lock file and retry.
at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:221)
at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:292)
at org.eclipse.jgit.dircache.DirCache.lock(DirCache.java:258)
at org.eclipse.jgit.lib.Repository.lockDirCache(Repository.java:1282)
at org.eclipse.jgit.api.ResetCommand.checkoutIndex(ResetCommand.java:407)
...
(12 additional frame(s) were not displayed)
JGitInternalException: Exception caught during execution of reset command. Cannot lock /data/git-storage/628e37967901344ba8d296e3/629f4d18360bee1cd628fe46/suzuya-studio-rental/.git/index. Ensure that no other process has an open file handle on the lock file /data/git-storage/628e37967901344ba8d296e3/629f4d18360bee1cd628fe46/suzuya-studio-rental/.git/index.lock, then you may delete the lock file and retry.
at org.eclipse.jgit.api.ResetCommand.call(ResetCommand.java:209)
@AnaghHegde @vuiets we're suddenly seeing a lot of these sentry issues. Can we fix on priority? What has changed here?
@Nikhil-Nandagopal The sudden spike in the sentry was due to efs. We noticed a sudden spike in efs throughput yesterday and this caused the users to not be able to use the git feature. Hence the sentry had so many cannot lock file(as java process could not access the file system) errors in sentry. PR is done, just waiting for Arpits final review and then its good to merge to release.
@AnaghHegde could we close this if it's merged?
Yeah can we please fix this? I see this very often and I can even reproduce this on prod
@AnaghHegde to fix one flaky test for this, on a PR raised for this.
#12174
This will be fixed after the new export/import infra changes we working on.