From 3286e680637032ed35da90c8600fddde2b831e3a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 22 Oct 2018 12:39:31 -0400 Subject: [PATCH] analysis --- ...omment_1_005874771ab14efb94c4a739da31b523._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/bugs/initial_get_-J_on_exported_S3_bucket_fails/comment_1_005874771ab14efb94c4a739da31b523._comment diff --git a/doc/bugs/initial_get_-J_on_exported_S3_bucket_fails/comment_1_005874771ab14efb94c4a739da31b523._comment b/doc/bugs/initial_get_-J_on_exported_S3_bucket_fails/comment_1_005874771ab14efb94c4a739da31b523._comment new file mode 100644 index 0000000000..98b3ec2f9a --- /dev/null +++ b/doc/bugs/initial_get_-J_on_exported_S3_bucket_fails/comment_1_005874771ab14efb94c4a739da31b523._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2018-10-22T16:37:06Z" + content=""" +Seems that the problem is that updateExportTreeFromLog gets started by the +first thread, and once it's started it won't be run again. Meanwhile, +other threads try to access the export database that populates. + +So, just needs some inter-thread locking.. +"""]]