Uploaded image for project: 'ModeShape'
  1. ModeShape
  2. MODE-1854

Indexing took too much time to finish when using explicit JTA transaction compared to no transaction

    XMLWordPrintable

Details

    Description

      When creating nodes under explicit JTA transaction, it took much more time to save compared to non transaction.
      When query functionality is disabled, the time spent in both cases are almost identical (In my real case, the transaction case even run a little bit faster than non transaction case). Therefore, I think it should be a Hibernate Search/Lucence integration issue.

      See attached profile data for details
      In the non-transaction case, there are 8 [Lucene Merge Thread] threads created.
      However, in the transaction case, there are 89 [Lucene Merge Thread] threads created which almost ten times than previous case.

      Attachments

        1. jprofiler_mode_1822.zip
          329 kB
        2. MODE-1822.zip
          252 kB
        3. no-transaction.nps
          37 kB
        4. no-transaction.png
          no-transaction.png
          103 kB
        5. transaction.nps
          39 kB
        6. transaction.png
          transaction.png
          99 kB

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. MODE-1837 Sometimes query returns duplicated records after commiting a transaction that contains VersionManager.checkin() call when using a real JTA transaction manager

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. MODE-1822 VersionManager.checkin throws exception in the transaction when using JTA transaction manager

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. MODE-1837 Sometimes query returns duplicated records after commiting a transaction that contains VersionManager.checkin() call when using a real JTA transaction manager

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              hchiorean Horia Chiorean (Inactive)
              ozhou_jira Oliver Zhou (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: