Hi VictorWarner,
Could you clarify for me the exact behavior you are observing with IMAP indexing under the 8.2 beta? From your description, it sounds like the initial indexing cycle of your IMAP(s) account(s) may never complete successfully(?). Or, does the initial scan complete, but subsequent (incremental) scans commence in advance of the 60 minute schedule? X1 connectors are desinged to operate in the following manner. If you are observing behavior different from this, we'd be very interested to hear the details, and to review a set of x1 logs.
Expected behavior of IMAP connectors:
1. the user may configure one or more email connectors based on IMAP (Gmail, Outlook.com, Yahoo!, etc.)
2. to add an IMAP source, the user selects the appropriate email connector from the Manage Data Sources panel, and provides the required account configuration details
3. after selecting the email folders the user wishes X1 to index, the user click OK to finalize connector settings
4. the newly configured source connector is placed in the index queue. Once other active scanners have completed indexing, the IMAP connector will initiate indexing of its account(s)
5. the initial indexing cycle will continue until all of the content residing under the folders the user enabled for indexing have been consumed into index
6. the IMAP scanner will perform an incremental scan to update the index with additions/deletions at an interval defined by the collection schedule (e.g. Every X minutes; Every day at X hour; Never repeat). If the collection schedule is set to Every 30 minutes, this means that an incremental scan cycle should commence 30 minutes after the previous scan cycle has completed.
7. Although a scanner may have been configured with collection schedule, this setting may be overridden by clicking the Start Indexing (Play > control), or by clicking Resume All (from the status menu at the lower right of the GUI).
Please let us know if you are observing indexing behavior inconsistent with this description.
Also, if you are observing that the IMAP scanner(s) are consuming a lot of CPU &/or memory resource, could you please share your system specs (number of CPUs, RAM, OS & bitness)?
Thank you for taking the time to share your observations!
Best Regards,
Alan Anderson
Director Quality Assurance
Could you clarify for me the exact behavior you are observing with IMAP indexing under the 8.2 beta? From your description, it sounds like the initial indexing cycle of your IMAP(s) account(s) may never complete successfully(?). Or, does the initial scan complete, but subsequent (incremental) scans commence in advance of the 60 minute schedule? X1 connectors are desinged to operate in the following manner. If you are observing behavior different from this, we'd be very interested to hear the details, and to review a set of x1 logs.
Expected behavior of IMAP connectors:
1. the user may configure one or more email connectors based on IMAP (Gmail, Outlook.com, Yahoo!, etc.)
2. to add an IMAP source, the user selects the appropriate email connector from the Manage Data Sources panel, and provides the required account configuration details
3. after selecting the email folders the user wishes X1 to index, the user click OK to finalize connector settings
4. the newly configured source connector is placed in the index queue. Once other active scanners have completed indexing, the IMAP connector will initiate indexing of its account(s)
5. the initial indexing cycle will continue until all of the content residing under the folders the user enabled for indexing have been consumed into index
6. the IMAP scanner will perform an incremental scan to update the index with additions/deletions at an interval defined by the collection schedule (e.g. Every X minutes; Every day at X hour; Never repeat). If the collection schedule is set to Every 30 minutes, this means that an incremental scan cycle should commence 30 minutes after the previous scan cycle has completed.
7. Although a scanner may have been configured with collection schedule, this setting may be overridden by clicking the Start Indexing (Play > control), or by clicking Resume All (from the status menu at the lower right of the GUI).
Please let us know if you are observing indexing behavior inconsistent with this description.
Also, if you are observing that the IMAP scanner(s) are consuming a lot of CPU &/or memory resource, could you please share your system specs (number of CPUs, RAM, OS & bitness)?
Thank you for taking the time to share your observations!
Best Regards,
Alan Anderson
Director Quality Assurance