• 1
    • Not defined

      With Optimize managing index configuration with instance archiving, the shard count configuration should not be applied to archive process instance indices, as these will be rolled over when appropriate

      ATs:

      • Only create single-sharded archive indices, regardless of the configured value of the number of shards for instance indices

        This is the controller panel for Smart Panels app

            [OPT-5932] Update the shard count configuration option

            Joshua Windels created issue -
            Joshua Windels made changes -
            Summary Original: Deprecate the shard count configuration option New: Update the shard count configuration option
            Sebastian Bathke made changes -
            Labels Original: PM SUPPORT blog configuration current_release elasticsearch potential_for_3.8 New: PM SUPPORT blog configuration current_release elasticsearch next_release potential_for_3.8
            Sebastian Bathke made changes -
            Labels Original: PM SUPPORT blog configuration current_release elasticsearch next_release potential_for_3.8 New: PM SUPPORT blog configuration elasticsearch next_release potential_for_3.8
            Sebastian Bathke made changes -
            Labels Original: PM SUPPORT blog configuration elasticsearch next_release potential_for_3.8 New: PM SUPPORT blog configuration current_release elasticsearch next_release potential_for_3.8
            Sebastian Bathke made changes -
            Labels Original: PM SUPPORT blog configuration current_release elasticsearch next_release potential_for_3.8 New: PM SUPPORT blog configuration current_release elasticsearch potential_for_3.8
            Joshua Windels made changes -
            Status Original: Open [ 1 ] New: In Development [ 10312 ]
            Joshua Windels made changes -
            Description Original: With Optimize managing index configuration with instance archiving, the shard count configuration is no longer applicable for process instance indices. We should either update the documentation to make it clear that it only applies to decision indices, or alternatively we could possibly deprecate the whole configuration altogether

            *ATs:*
             * Publish that the shard configuration option is no longer applicable to process instance indices
            New: With Optimize managing index configuration with instance archiving, the shard count configuration should not be applied to archive process instance indices, as these will be rolled over when appropriate

            *ATs:*
             * Only create single-sharded archive indices, regardless of the configured value of the number of shards for instance indices
            Joshua Windels made changes -
            Mentioned Roles
            Joshua Windels made changes -
            Mentioned Groups

              Unassigned Unassigned
              joshua.windels Joshua Windels
              Joshua Windels Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: