[jira] [Comment Edited] (IGNITE-12051) Update javadoc for the IgniteKernal class
[
https://issues.apache.org/jira/browse/IGNITE-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905875#comment-16905875
]
Ivan Pavlukhin edited comment on IGNITE-12051 at 8/13/19 6:48 AM:
--
[~Mmuzaf], I left few comments on GitHub.
was (Author: pavlukhin):
[~Mmuzaf], I left several comments on GitHub.
> Update javadoc for the IgniteKernal class
> -
>
> Key: IGNITE-12051
> URL: https://issues.apache.org/jira/browse/IGNITE-12051
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> Update all ambiguous an empty javadoc comments, such as:
> {code}
> /** */
> /** Periodic starvation check interval. */
> private static final long PERIODIC_STARVATION_CHECK_FREQ = 1000 * 30;
> /** Long jvm pause detector. */
> private LongJVMPauseDetector longJVMPauseDetector;
> /** Scheduler. */
> private IgniteScheduler scheduler;
> /** Stop guard. */
> private final AtomicBoolean stopGuard = new AtomicBoolean();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-12051) Update javadoc for the IgniteKernal class
[
https://issues.apache.org/jira/browse/IGNITE-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905875#comment-16905875
]
Ivan Pavlukhin commented on IGNITE-12051:
-
[~Mmuzaf], I left several comments on GitHub.
> Update javadoc for the IgniteKernal class
> -
>
> Key: IGNITE-12051
> URL: https://issues.apache.org/jira/browse/IGNITE-12051
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 5.5h
> Remaining Estimate: 0h
>
> Update all ambiguous an empty javadoc comments, such as:
> {code}
> /** */
> /** Periodic starvation check interval. */
> private static final long PERIODIC_STARVATION_CHECK_FREQ = 1000 * 30;
> /** Long jvm pause detector. */
> private LongJVMPauseDetector longJVMPauseDetector;
> /** Scheduler. */
> private IgniteScheduler scheduler;
> /** Stop guard. */
> private final AtomicBoolean stopGuard = new AtomicBoolean();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (IGNITE-12057) Persistence files are stored to temp dir
[ https://issues.apache.org/jira/browse/IGNITE-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-12057: - Fix Version/s: (was: 2.8) 2.7.6 > Persistence files are stored to temp dir > > > Key: IGNITE-12057 > URL: https://issues.apache.org/jira/browse/IGNITE-12057 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Anton Kalashnikov >Priority: Critical > Fix For: 2.7.6 > > > h2. Description > Check this thread: > [https://stackoverflow.com/questions/56951913/ignite-persistent-schema-tables-disappeared-sometimes/56977212#56977212] > This prospect almost dropped us because the company could figure out why > persistence files disappear upon restarts. They turned off WARN logging level > and could see our warning saying that the files are written to such a > directory. > I've updated Ignite docs: > [https://apacheignite.readme.io/docs/distributed-persistent-store#section-persistence-path-management] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12046) [IEP-35] LongMetric interface contains redundant methods.
[
https://issues.apache.org/jira/browse/IGNITE-12046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905668#comment-16905668
]
Andrey Gura commented on IGNITE-12046:
--
[~NIzhikov] Could you please review?
> [IEP-35] LongMetric interface contains redundant methods.
> -
>
> Key: IGNITE-12046
> URL: https://issues.apache.org/jira/browse/IGNITE-12046
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Trivial
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following methods on {{LongMetric}} interface a redundant and have the
> same functionality:
> * {{get}}
> * {{longValue}}
> Mentioned methods should be removed.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-12046) [IEP-35] LongMetric interface contains redundant methods.
[
https://issues.apache.org/jira/browse/IGNITE-12046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905666#comment-16905666
]
Ignite TC Bot commented on IGNITE-12046:
{panel:title=Branch: [pull/6751/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4492028&buildTypeId=IgniteTests24Java8_RunAll]
> [IEP-35] LongMetric interface contains redundant methods.
> -
>
> Key: IGNITE-12046
> URL: https://issues.apache.org/jira/browse/IGNITE-12046
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Trivial
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following methods on {{LongMetric}} interface a redundant and have the
> same functionality:
> * {{get}}
> * {{longValue}}
> Mentioned methods should be removed.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Issue Comment Deleted] (IGNITE-12046) [IEP-35] LongMetric interface contains redundant methods.
[
https://issues.apache.org/jira/browse/IGNITE-12046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-12046:
-
Comment: was deleted
(was: {panel:title=Branch: [pull/6751/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4492559]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4492028&buildTypeId=IgniteTests24Java8_RunAll])
> [IEP-35] LongMetric interface contains redundant methods.
> -
>
> Key: IGNITE-12046
> URL: https://issues.apache.org/jira/browse/IGNITE-12046
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Trivial
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following methods on {{LongMetric}} interface a redundant and have the
> same functionality:
> * {{get}}
> * {{longValue}}
> Mentioned methods should be removed.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-12046) [IEP-35] LongMetric interface contains redundant methods.
[
https://issues.apache.org/jira/browse/IGNITE-12046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905513#comment-16905513
]
Ignite TC Bot commented on IGNITE-12046:
{panel:title=Branch: [pull/6751/head] Base: [master] : Possible Blockers
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 6{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4492559]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4492028&buildTypeId=IgniteTests24Java8_RunAll]
> [IEP-35] LongMetric interface contains redundant methods.
> -
>
> Key: IGNITE-12046
> URL: https://issues.apache.org/jira/browse/IGNITE-12046
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Trivial
> Labels: IEP-35
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The following methods on {{LongMetric}} interface a redundant and have the
> same functionality:
> * {{get}}
> * {{longValue}}
> Mentioned methods should be removed.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-12051) Update javadoc for the IgniteKernal class
[
https://issues.apache.org/jira/browse/IGNITE-12051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905308#comment-16905308
]
Maxim Muzafarov commented on IGNITE-12051:
--
[~Pavlukhin]
I've updated the class Javadoc. Can you check it again?
> Update javadoc for the IgniteKernal class
> -
>
> Key: IGNITE-12051
> URL: https://issues.apache.org/jira/browse/IGNITE-12051
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Minor
> Fix For: 2.8
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> Update all ambiguous an empty javadoc comments, such as:
> {code}
> /** */
> /** Periodic starvation check interval. */
> private static final long PERIODIC_STARVATION_CHECK_FREQ = 1000 * 30;
> /** Long jvm pause detector. */
> private LongJVMPauseDetector longJVMPauseDetector;
> /** Scheduler. */
> private IgniteScheduler scheduler;
> /** Stop guard. */
> private final AtomicBoolean stopGuard = new AtomicBoolean();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (IGNITE-12057) Persistence files are stored to temp dir
[ https://issues.apache.org/jira/browse/IGNITE-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Kalashnikov reassigned IGNITE-12057: -- Assignee: Anton Kalashnikov > Persistence files are stored to temp dir > > > Key: IGNITE-12057 > URL: https://issues.apache.org/jira/browse/IGNITE-12057 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Anton Kalashnikov >Priority: Critical > Fix For: 2.8 > > > h2. Description > Check this thread: > [https://stackoverflow.com/questions/56951913/ignite-persistent-schema-tables-disappeared-sometimes/56977212#56977212] > This prospect almost dropped us because the company could figure out why > persistence files disappear upon restarts. They turned off WARN logging level > and could see our warning saying that the files are written to such a > directory. > I've updated Ignite docs: > [https://apacheignite.readme.io/docs/distributed-persistent-store#section-persistence-path-management] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12042) Atempt to remove entries from fully populated data region may result in IgineOutOfMemoryException
[ https://issues.apache.org/jira/browse/IGNITE-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905172#comment-16905172 ] Pavel Pereslegin commented on IGNITE-12042: --- [~ivan.glukos], [~slava.koptilin] Since you asked my opinion, I must say, that from my point of view this change looks like a workaround, and it seems unworkable for concurrent updates. For now, I can't figure out a simple and bulletproof solution for the described problem, but, as I already mentioned, it would be better to perform this check from PageMemoryNoStoreImpl#allocatePage and keep current "recovery behavior" untouched. At least it’s better to place this check into AbstractFreeList - then there will be no need to do an additional search in freelist's hashmap and there will be no need to additionally calculate the row size. But since I don't have a good solution and there is no big difference in my proposal, I do not insist on any changes and I'm sure that you better know what is best for the product. > Atempt to remove entries from fully populated data region may result in > IgineOutOfMemoryException > - > > Key: IGNITE-12042 > URL: https://issues.apache.org/jira/browse/IGNITE-12042 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.7 >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > Removing entries from non-persistent data region may require allocating a new > data page in order to move a tracked page from one bucket of the free-list to > another one. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12061) Silently fail while try to recreate already existing index with differ inline_size.
Stanilovsky Evgeny created IGNITE-12061: --- Summary: Silently fail while try to recreate already existing index with differ inline_size. Key: IGNITE-12061 URL: https://issues.apache.org/jira/browse/IGNITE-12061 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.7.5, 2.7, 2.5 Reporter: Stanilovsky Evgeny Assignee: Stanilovsky Evgeny INLINE_SIZE differ from previous value is not correctly sets. 1. create index idx0(c1, c2) 2. drop idx0 3. create index idx0(c1, c2) inline_size 100; inline_size remains the same, in this case default = 10. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-11978) Javadoc enhancement for the ReadRepair feature.
[ https://issues.apache.org/jira/browse/IGNITE-11978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905154#comment-16905154 ] Anton Vinogradov commented on IGNITE-11978: --- [~slava.koptilin], just a reminder that I'm waiting for simplification. [~NIzhikov], just a reminder we need you vote :) > Javadoc enhancement for the ReadRepair feature. > --- > > Key: IGNITE-11978 > URL: https://issues.apache.org/jira/browse/IGNITE-11978 > Project: Ignite > Issue Type: Bug >Reporter: Vyacheslav Koptilin >Assignee: Vyacheslav Koptilin >Priority: Major > Labels: iep-31 > Fix For: 2.8 > > Time Spent: 4h 40m > Remaining Estimate: 0h > > The newly added `ReadRepair` feature requires Javadoc improvements. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption
[ https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905113#comment-16905113 ] Dmitriy Govorukhin commented on IGNITE-12060: - Merged to master. > Incorrect row size calculation, lead to tree corruption > --- > > Key: IGNITE-12060 > URL: https://issues.apache.org/jira/browse/IGNITE-12060 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > > We do not correctly calculate old row size and new row size for check > in-place update. One of them may include cacheId but other not. Size > dependent on shared group or not. > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption
[ https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-12060: Summary: Incorrect row size calculation, lead to tree corruption (was: Incorrect row size calculation, lead to tree corruption.) > Incorrect row size calculation, lead to tree corruption > --- > > Key: IGNITE-12060 > URL: https://issues.apache.org/jira/browse/IGNITE-12060 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > > We do not correctly calculate old row size and new row size for check > in-place update. One of them may include cacheId but other not. Size > dependent on shared group or not. > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption.
[ https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-12060: Description: We do not correctly calculate old row size and new row size for check in-place update. One of them may include cacheId but other not. Size dependent on shared group or not. org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow was: We do not correctly calculate old row size and new row size for check in-place update. One of them may include cacheId but other not. org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow > Incorrect row size calculation, lead to tree corruption. > > > Key: IGNITE-12060 > URL: https://issues.apache.org/jira/browse/IGNITE-12060 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > > We do not correctly calculate old row size and new row size for check > in-place update. One of them may include cacheId but other not. Size > dependent on shared group or not. > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption.
[ https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-12060: Ignite Flags: (was: Docs Required) > Incorrect row size calculation, lead to tree corruption. > > > Key: IGNITE-12060 > URL: https://issues.apache.org/jira/browse/IGNITE-12060 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > > We do not correctly calculate old row size and new row size for check > in-place update. One of them may include cacheId but other not. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption.
[ https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-12060: Description: We do not correctly calculate old row size and new row size for check in-place update. One of them may include cacheId but other not. > Incorrect row size calculation, lead to tree corruption. > > > Key: IGNITE-12060 > URL: https://issues.apache.org/jira/browse/IGNITE-12060 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > > We do not correctly calculate old row size and new row size for check > in-place update. One of them may include cacheId but other not. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption.
[ https://issues.apache.org/jira/browse/IGNITE-12060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-12060: Description: We do not correctly calculate old row size and new row size for check in-place update. One of them may include cacheId but other not. org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow was:We do not correctly calculate old row size and new row size for check in-place update. One of them may include cacheId but other not. > Incorrect row size calculation, lead to tree corruption. > > > Key: IGNITE-12060 > URL: https://issues.apache.org/jira/browse/IGNITE-12060 > Project: Ignite > Issue Type: Bug >Reporter: Dmitriy Govorukhin >Assignee: Dmitriy Govorukhin >Priority: Critical > Fix For: 2.8 > > > We do not correctly calculate old row size and new row size for check > in-place update. One of them may include cacheId but other not. > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#canUpdateOldRow -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12060) Incorrect row size calculation, lead to tree corruption.
Dmitriy Govorukhin created IGNITE-12060: --- Summary: Incorrect row size calculation, lead to tree corruption. Key: IGNITE-12060 URL: https://issues.apache.org/jira/browse/IGNITE-12060 Project: Ignite Issue Type: Bug Reporter: Dmitriy Govorukhin Assignee: Dmitriy Govorukhin Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12059) DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails
[ https://issues.apache.org/jira/browse/IGNITE-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-12059: Fix Version/s: 2.8 > DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration > fails > --- > > Key: IGNITE-12059 > URL: https://issues.apache.org/jira/browse/IGNITE-12059 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration > fails because validation was removed in IGNITE-9562. > Need to restore this validation. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (IGNITE-12016) Is there option to increase or decrease Ignite SQL Table backup count after its initialized?
[ https://issues.apache.org/jira/browse/IGNITE-12016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Gura resolved IGNITE-12016. -- Resolution: Not A Bug > Is there option to increase or decrease Ignite SQL Table backup count after > its initialized? > > > Key: IGNITE-12016 > URL: https://issues.apache.org/jira/browse/IGNITE-12016 > Project: Ignite > Issue Type: New Feature >Reporter: hirik >Priority: Major > > Hi, > We are working in a dynamic environment, based on the new nodes we should > update the backup count of existing SQL tables. is there any api available to > support this requirement? -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12059) DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails
[ https://issues.apache.org/jira/browse/IGNITE-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Shangareev updated IGNITE-12059: --- Ignite Flags: (was: Docs Required) > DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration > fails > --- > > Key: IGNITE-12059 > URL: https://issues.apache.org/jira/browse/IGNITE-12059 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration > fails because validation was removed in IGNITE-9562. > Need to restore this validation. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12059) DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails
[ https://issues.apache.org/jira/browse/IGNITE-12059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905066#comment-16905066 ] Eduard Shangareev commented on IGNITE-12059: https://ci.ignite.apache.org/viewQueued.html?itemId=4491407 > DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration > fails > --- > > Key: IGNITE-12059 > URL: https://issues.apache.org/jira/browse/IGNITE-12059 > Project: Ignite > Issue Type: Bug >Reporter: Eduard Shangareev >Assignee: Eduard Shangareev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration > fails because validation was removed in IGNITE-9562. > Need to restore this validation. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12021) Inserting date from Node.JS to a cache which has Java.SQL.Timestamp
[ https://issues.apache.org/jira/browse/IGNITE-12021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-12021: - Labels: Ignite Node.JS (was: Node.JS ignite,) > Inserting date from Node.JS to a cache which has Java.SQL.Timestamp > --- > > Key: IGNITE-12021 > URL: https://issues.apache.org/jira/browse/IGNITE-12021 > Project: Ignite > Issue Type: Bug > Components: cache, thin client >Affects Versions: 2.7 > Environment: We are in DEV right now. can't proceed to higher > environment with this show stopper >Reporter: Gaurav >Priority: Blocker > Labels: Ignite, Node.JS > > I have cache which has one field with type java.sql.Timestamp > > From, Node.JS i am inserting it as new Date(). > If the cache is empty the inserts are successful. Issue come when java > inserted few records in this cache (Java inserts java.sql.Timestamp) . Now , > if I run Node.JS program which tries to insert it gives me this error. > > Binary type has different field types [typeName=XYZCacheName, > fieldName=updateTime, fieldTypeName1=Timestamp, fieldTypeName2=Date] > > Please help, its stopped my work totally! > > P.S : JavaScript new Date() is itself a Timestamp, so cache should ideally > accept it as Timestamp and not Date. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12059) DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails
Eduard Shangareev created IGNITE-12059: -- Summary: DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails Key: IGNITE-12059 URL: https://issues.apache.org/jira/browse/IGNITE-12059 Project: Ignite Issue Type: Bug Reporter: Eduard Shangareev Assignee: Eduard Shangareev DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration fails because validation was removed in IGNITE-9562. Need to restore this validation. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-12011) MetricUpdater timeout can't be configured
[
https://issues.apache.org/jira/browse/IGNITE-12011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Gura updated IGNITE-12011:
-
Priority: Minor (was: Major)
> MetricUpdater timeout can't be configured
> -
>
> Key: IGNITE-12011
> URL: https://issues.apache.org/jira/browse/IGNITE-12011
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0
>Reporter: Max Shonichev
>Priority: Minor
> Fix For: 3.0
>
>
> {noformat}
> /** Metrics update frequency. */
> private static final long METRICS_UPDATE_FREQ = 3000;
> ...
> /** {@inheritDoc} */
> @Override protected void onKernalStart0() throws IgniteCheckedException {
> metricsUpdateTask = ctx.timeout().schedule(new MetricsUpdater(),
> METRICS_UPDATE_FREQ, METRICS_UPDATE_FREQ);
> }
> {noformat}
> Would be great if metric updater timeout was externally configured.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-10808) Discovery message queue may build up with TcpDiscoveryMetricsUpdateMessage
[
https://issues.apache.org/jira/browse/IGNITE-10808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904978#comment-16904978
]
Ignite TC Bot commented on IGNITE-10808:
{panel:title=Branch: [pull/5771/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4457883&buildTypeId=IgniteTests24Java8_RunAll]
> Discovery message queue may build up with TcpDiscoveryMetricsUpdateMessage
> --
>
> Key: IGNITE-10808
> URL: https://issues.apache.org/jira/browse/IGNITE-10808
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Stanislav Lukyanov
>Assignee: Denis Mekhanikov
>Priority: Major
> Labels: discovery
> Fix For: 2.8
>
> Attachments: IgniteMetricsOverflowTest.java
>
>
> A node receives a new metrics update message every `metricsUpdateFrequency`
> milliseconds, and the message will be put at the top of the queue (because it
> is a high priority message).
> If processing one message takes more than `metricsUpdateFrequency` then
> multiple `TcpDiscoveryMetricsUpdateMessage` will be in the queue. A long
> enough delay (e.g. caused by a network glitch or GC) may lead to the queue
> building up tens of metrics update messages which are essentially useless to
> be processed. Finally, if processing a message on average takes a little more
> than `metricsUpdateFrequency` (even for a relatively short period of time,
> say, for a minute due to network issues) then the message worker will end up
> processing only the metrics updates and the cluster will essentially hang.
> Reproducer is attached. In the test, the queue first builds up and then very
> slowly being teared down, causing "Failed to wait for PME" messages.
> Need to change ServerImpl's SocketReader not to put another metrics update
> message to the top of the queue if it already has one (or replace the one at
> the top with new one).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-5714) Implementation of suspend/resume for pessimistic transactions
[ https://issues.apache.org/jira/browse/IGNITE-5714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16904961#comment-16904961 ] Igor Seliverstov commented on IGNITE-5714: -- [~alex_pl], now it looks much better, I have no objections to merge the PR. > Implementation of suspend/resume for pessimistic transactions > - > > Key: IGNITE-5714 > URL: https://issues.apache.org/jira/browse/IGNITE-5714 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Alexey Kuznetsov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: iep-34 > Time Spent: 4.5h > Remaining Estimate: 0h > > Support transaction suspend()\resume() operations for pessimistic > transactions. Resume can be called in another thread. >_+But there is a problem+_: Imagine, we started pessimistic transaction in > thread T1 and then perform put operation, which leads to sending > GridDistributedLockRequest to another node. Lock request contains thread id > of the transaction. Then we call suspend, resume in another thread and we > also must send messages to other nodes to change thread id. > It seems complicated task.It’s better to get rid of sending thread id to the > nodes. > We can use transaction xid on other nodes instead of thread id. Xid is sent > to nodes in GridDistributedLockRequest#nearXidVer >_+Proposed solution+_ : On remote nodes instead of thread id of near > transaction GridDistributedLockRequest#threadId use its xid > GridDistributedLockRequest#nearXidVer. > Remove usages of near transaction's thread id on remote nodes. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12058) AtomicReference issue with different userVersions
Niels Ejrnæs created IGNITE-12058:
-
Summary: AtomicReference issue with different userVersions
Key: IGNITE-12058
URL: https://issues.apache.org/jira/browse/IGNITE-12058
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7.5
Reporter: Niels Ejrnæs
Attachments: ignite-playground.tar.gz
When running DeploymentMode CONTINUOUS or SHARED and connecting a client node
with a different userVersion from the server nodes - IgniteAtomicLongs and
IgniteAtomicReferences cannot be fetched directly from Ignite.
{code:java}
IgniteAtomicLong atomicLong = ignite.atomicLong("long", 0, false);
IgniteAtomicReference atomicReference =
ignite.atomicReference("reference", "", false);
{code}
It throws an Exception {noformat}
SEVERE: Error deserializing job response: GridJobExecuteResponse
[nodeId=b52607ba-b6d1-47bc-983c-380af8a679bd,
sesId=f13d9c48c61-0fabe984-ecf1-4acf-84ac-3bdd478405f7,
jobId=023d9c48c61-0fabe984-ecf1-4acf-84ac-3bdd478405f7, gridEx=null,
isCancelled=false, retry=null]
class org.apache.ignite.IgniteCheckedException: Failed to unmarshal object with
optimized marshaller
at
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:10147)
...
Caused by: class org.apache.ignite.internal.IgniteDeploymentCheckedException:
Failed to obtain deployment for class:
org.apache.ignite.configuration.CacheConfiguration$IgniteAllNodesPredicate
...
{noformat}
It works if you use a compute job to fetch it.
{code:java}
long remoteLong = ignite.compute().call(() -> { return
ignite.atomicLong("long", 0, false).get(); });
ignite.compute().call(() -> { return ignite.atomicLong("long", 0,
false).incrementAndGet(); });
String remoteReference = ignite.compute().call(() -> { return
ignite.atomicReference("reference", "", false).get(); });
{code}
I've attached a small reproducer project.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
