You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Pavlov (JIRA)" <ji...@apache.org> on 2019/01/17 18:27:00 UTC
[jira] [Updated] (IGNITE-10942) [TC Bot] Optimize background JIRA
tickets sync
[ https://issues.apache.org/jira/browse/IGNITE-10942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Pavlov updated IGNITE-10942:
------------------------------------
Summary: [TC Bot] Optimize background JIRA tickets sync (was: [TC Bot] Optimize backround JIRA tickets sync)
> [TC Bot] Optimize background JIRA tickets sync
> ----------------------------------------------
>
> Key: IGNITE-10942
> URL: https://issues.apache.org/jira/browse/IGNITE-10942
> Project: Ignite
> Issue Type: Task
> Reporter: Dmitriy Pavlov
> Assignee: Dmitriy Pavlov
> Priority: Major
>
> JIRA sync is now performed in not an efficient manner.
> All project data is reloaded every 15 minutes, and this may create additional pressure for 3rd party services.
> Introduce incremental updates (update is running only until the first non-modified element found) and full updates.
> Check ticket data modification before saving into Ignite DB (will safe WAL & page store pressure).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)