[jira] [Commented] (IGNITE-12477) Slow test in Queries 1 test suite
[
https://issues.apache.org/jira/browse/IGNITE-12477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001633#comment-17001633
]
Ignite TC Bot commented on IGNITE-12477:
{panel:title=Branch: [pull/7177/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=4861264buildTypeId=IgniteTests24Java8_RunAll]
> Slow test in Queries 1 test suite
> -
>
> Key: IGNITE-12477
> URL: https://issues.apache.org/jira/browse/IGNITE-12477
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> "Queries 1" suite execution time can be optimized.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12476) Slow test in Continuous Query 1 test suite
[ https://issues.apache.org/jira/browse/IGNITE-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001632#comment-17001632 ] Ivan Pavlukhin commented on IGNITE-12476: - TC bot report is not a problem because mentioned tests was simply moved from CQ 1 suite to CQ 2 suite. > Slow test in Continuous Query 1 test suite > -- > > Key: IGNITE-12476 > URL: https://issues.apache.org/jira/browse/IGNITE-12476 > Project: Ignite > Issue Type: Task >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > "Continuous Query 1" suite execution time can be optimized. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12476) Slow test in Continuous Query 1 test suite
[
https://issues.apache.org/jira/browse/IGNITE-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001631#comment-17001631
]
Ignite TC Bot commented on IGNITE-12476:
{panel:title=Branch: [pull/7176/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=4862834]]
* IgniteCacheQuerySelfTestSuite4:
CacheContinuousQueryFailoverAtomicNearEnabledSelfTest.testMultiThreadedFailover
- New test duration 62s is more that 1 minute
* IgniteCacheQuerySelfTestSuite4:
CacheContinuousQueryFailoverAtomicNearEnabledSelfTest.testFailoverStartStopBackup
- New test duration 68s is more that 1 minute
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4861380buildTypeId=IgniteTests24Java8_RunAll]
> Slow test in Continuous Query 1 test suite
> --
>
> Key: IGNITE-12476
> URL: https://issues.apache.org/jira/browse/IGNITE-12476
> Project: Ignite
> Issue Type: Task
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> "Continuous Query 1" suite execution time can be optimized.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12120) Change log level in GridCacheWritebehindStore
[
https://issues.apache.org/jira/browse/IGNITE-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001158#comment-17001158
]
Ignite TC Bot commented on IGNITE-12120:
{panel:title=Branch: [pull/7170/head] Base: [master] : Possible Blockers
(16)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4862079]]
* exe: PersistenceTest.TestWalDisableEnable - Test has low fail rate in base
branch 0,0% and is not flaky
{color:#d04437}Streamers{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4862023]]
* IgniteStormStreamerSelfTestSuite:
StormIgniteStreamerSelfTest.testStormStreamerIgniteBolt - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Cache 5{color} [[tests
6|https://ci.ignite.apache.org/viewLog.html?buildId=4862062]]
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillCrdWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillThreeNodesWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsAfterKillCrdWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeWithBackupsWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheTestSuite5:
IgniteCachePartitionLossPolicySelfTest.testReadWriteSafeAfterKillTwoNodesWithPersistence[TRANSACTIONAL]
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Thin Client: Java{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4862016]]
* ClientTestSuite: ReliabilityTest.testFailover - Test has low fail rate in
base branch 0,0% and is not flaky
{color:#d04437}Cache 1{color} [[tests 5 Out Of Memory Error
|https://ci.ignite.apache.org/viewLog.html?buildId=4862058]]
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testLocalDataStreamerDedicatedThreadPool
- Test has low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testCustomUserUpdater - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testLoaderApi - Test has low fail
rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testReplicatedIsolated - Test has
low fail rate in base branch 0,0% and is not flaky
* IgniteBinaryCacheTestSuite:
DataStreamProcessorPersistenceBinarySelfTest.testPartitionedMultiThreaded -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Activate / Deactivate Cluster{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4861999]]
* IgniteStandByClusterSuite:
IgniteBaselineAffinityTopologyActivationTest.testNodeJoinsDuringPartitionMapExchange
- Test has low fail rate in base branch 0,0% and is not flaky
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4862109buildTypeId=IgniteTests24Java8_RunAll]
> Change log level in GridCacheWritebehindStore
> -
>
> Key: IGNITE-12120
> URL: https://issues.apache.org/jira/browse/IGNITE-12120
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.5
>Reporter: Sunny Chan
>Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the
> [GridCacheWriteBehindStore|https://github.com/apache/ignite/blob/7e73098d4d6e3d5f78326cb11dac7e083a2312dd/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L893],
> when the updateStore failed to write to underlying store, it logs this as
> error:
> {{LT.error(log, e, "Unable to update underlying store: " + store);}}
> After this line logged the error, it would return false so that it would
> retry the store (by returning false).
> While later on in the updatStore function, when the writeCache overflows, it
> would log this:
> {{log.warning("Failed to update store (value will be lost as current buffer
> size is greater " + …}}
> then it will remove the failed entry.
> I think the severity of the log messages is not right, as the fail update
> would
[jira] [Resolved] (IGNITE-2323) Improvments for http client
[ https://issues.apache.org/jira/browse/IGNITE-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-2323. Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Done > Improvments for http client > --- > > Key: IGNITE-2323 > URL: https://issues.apache.org/jira/browse/IGNITE-2323 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Semen Boikov >Assignee: Chandresh Pancholi >Priority: Critical > > Need to fix following issues in http code used in nodejs client: > - request timeout is hardcoded, need to make it configurable > - need to handle session token which can be returned by ignite > - X-Signature is calculated for each, probably can do it only once -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-2323) Improvments for http client
[ https://issues.apache.org/jira/browse/IGNITE-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-2323. -- > Improvments for http client > --- > > Key: IGNITE-2323 > URL: https://issues.apache.org/jira/browse/IGNITE-2323 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Semen Boikov >Assignee: Chandresh Pancholi >Priority: Critical > > Need to fix following issues in http code used in nodejs client: > - request timeout is hardcoded, need to make it configurable > - need to handle session token which can be returned by ignite > - X-Signature is calculated for each, probably can do it only once -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-2361) Implement possibility to run java task by name
[ https://issues.apache.org/jira/browse/IGNITE-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-2361. -- > Implement possibility to run java task by name > -- > > Key: IGNITE-2361 > URL: https://issues.apache.org/jira/browse/IGNITE-2361 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Semen Boikov >Priority: Major > > Need to added in Nodejs client possiblity to run java task by name with > optional argument (i.e. wrapper for java API IgniteCompute.execute(String > taskName, T arg)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-2361) Implement possibility to run java task by name
[ https://issues.apache.org/jira/browse/IGNITE-2361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-2361. Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Done > Implement possibility to run java task by name > -- > > Key: IGNITE-2361 > URL: https://issues.apache.org/jira/browse/IGNITE-2361 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Semen Boikov >Priority: Major > > Need to added in Nodejs client possiblity to run java task by name with > optional argument (i.e. wrapper for java API IgniteCompute.execute(String > taskName, T arg)). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-1051) node.js: create nodejs examples
[ https://issues.apache.org/jira/browse/IGNITE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-1051. Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Done > node.js: create nodejs examples > --- > > Key: IGNITE-1051 > URL: https://issues.apache.org/jira/browse/IGNITE-1051 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Semen Boikov >Priority: Major > Attachments: ignite-961_ignite-1051.patch > > > Need to create examples for all implemented nodejs features. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-966) node.js: documentation on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-966. - > node.js: documentation on readme.io > --- > > Key: IGNITE-966 > URL: https://issues.apache.org/jira/browse/IGNITE-966 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > http://apacheignite.readme.io/v1.2/docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-2309) Implement security permissions checks for create/destory cache operations
[ https://issues.apache.org/jira/browse/IGNITE-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-2309. Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Done > Implement security permissions checks for create/destory cache operations > - > > Key: IGNITE-2309 > URL: https://issues.apache.org/jira/browse/IGNITE-2309 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Semen Boikov >Priority: Critical > > Currenctly there is no security checks for create/destroy cache operations > (need to add these checks on client and servers). There are some releated > changes in ignite-961-permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-1051) node.js: create nodejs examples
[ https://issues.apache.org/jira/browse/IGNITE-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-1051. -- > node.js: create nodejs examples > --- > > Key: IGNITE-1051 > URL: https://issues.apache.org/jira/browse/IGNITE-1051 > Project: Ignite > Issue Type: Sub-task > Components: general >Reporter: Semen Boikov >Priority: Major > Attachments: ignite-961_ignite-1051.patch > > > Need to create examples for all implemented nodejs features. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-966) node.js: documentation on readme.io
[ https://issues.apache.org/jira/browse/IGNITE-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-966. --- Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Done > node.js: documentation on readme.io > --- > > Key: IGNITE-966 > URL: https://issues.apache.org/jira/browse/IGNITE-966 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > http://apacheignite.readme.io/v1.2/docs -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-2309) Implement security permissions checks for create/destory cache operations
[ https://issues.apache.org/jira/browse/IGNITE-2309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-2309. -- > Implement security permissions checks for create/destory cache operations > - > > Key: IGNITE-2309 > URL: https://issues.apache.org/jira/browse/IGNITE-2309 > Project: Ignite > Issue Type: Sub-task > Components: cache >Reporter: Semen Boikov >Priority: Critical > > Currenctly there is no security checks for create/destroy cache operations > (need to add these checks on client and servers). There are some releated > changes in ignite-961-permissions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-963) node.js: implement mapreduce support
[ https://issues.apache.org/jira/browse/IGNITE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-963. - > node.js: implement mapreduce support > > > Key: IGNITE-963 > URL: https://issues.apache.org/jira/browse/IGNITE-963 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-965) node.js: provide npm package
[ https://issues.apache.org/jira/browse/IGNITE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-965. --- Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Done > node.js: provide npm package > > > Key: IGNITE-965 > URL: https://issues.apache.org/jira/browse/IGNITE-965 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > Need to investigate how packages are built and shared. > The result should be a script or automated procedure that build and share the > package -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-965) node.js: provide npm package
[ https://issues.apache.org/jira/browse/IGNITE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-965. - > node.js: provide npm package > > > Key: IGNITE-965 > URL: https://issues.apache.org/jira/browse/IGNITE-965 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > Need to investigate how packages are built and shared. > The result should be a script or automated procedure that build and share the > package -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-964) node.js: provide ability to run queries
[ https://issues.apache.org/jira/browse/IGNITE-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-964. --- Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Done > node.js: provide ability to run queries > --- > > Key: IGNITE-964 > URL: https://issues.apache.org/jira/browse/IGNITE-964 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > the implementation will require adding a special handler to HTTP REST > subsystem -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-964) node.js: provide ability to run queries
[ https://issues.apache.org/jira/browse/IGNITE-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-964. - > node.js: provide ability to run queries > --- > > Key: IGNITE-964 > URL: https://issues.apache.org/jira/browse/IGNITE-964 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > the implementation will require adding a special handler to HTTP REST > subsystem -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-962) node.js: provide json cache object implementation
[ https://issues.apache.org/jira/browse/IGNITE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-962. --- Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Resolved > node.js: provide json cache object implementation > - > > Key: IGNITE-962 > URL: https://issues.apache.org/jira/browse/IGNITE-962 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > * check if we can optimize strings store with storing byte arrays > * implement SQL indexing support for new object -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-962) node.js: provide json cache object implementation
[ https://issues.apache.org/jira/browse/IGNITE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-962. - No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client > node.js: provide json cache object implementation > - > > Key: IGNITE-962 > URL: https://issues.apache.org/jira/browse/IGNITE-962 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > > * check if we can optimize strings store with storing byte arrays > * implement SQL indexing support for new object -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-963) node.js: implement mapreduce support
[ https://issues.apache.org/jira/browse/IGNITE-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-963. --- Release Note: No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client Resolution: Won't Fix > node.js: implement mapreduce support > > > Key: IGNITE-963 > URL: https://issues.apache.org/jira/browse/IGNITE-963 > Project: Ignite > Issue Type: Sub-task > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (IGNITE-961) Provide Basic NodeJS Integration
[ https://issues.apache.org/jira/browse/IGNITE-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda closed IGNITE-961. - > Provide Basic NodeJS Integration > > > Key: IGNITE-961 > URL: https://issues.apache.org/jira/browse/IGNITE-961 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-961) Provide Basic NodeJS Integration
[ https://issues.apache.org/jira/browse/IGNITE-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001040#comment-17001040 ] Denis A. Magda commented on IGNITE-961: --- No longer relevant. Node.JS was supported using a thin client protocol: https://apacheignite.readme.io/docs/nodejs-thin-client > Provide Basic NodeJS Integration > > > Key: IGNITE-961 > URL: https://issues.apache.org/jira/browse/IGNITE-961 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-961) Provide Basic NodeJS Integration
[ https://issues.apache.org/jira/browse/IGNITE-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda resolved IGNITE-961. --- Resolution: Fixed > Provide Basic NodeJS Integration > > > Key: IGNITE-961 > URL: https://issues.apache.org/jira/browse/IGNITE-961 > Project: Ignite > Issue Type: New Feature > Components: clients >Reporter: Yakov Zhdanov >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-640) Implement IgniteMultimap data structures
[
https://issues.apache.org/jira/browse/IGNITE-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001038#comment-17001038
]
Denis A. Magda commented on IGNITE-640:
---
[~aakhmedov], are you planning to continue with this task? If you don't have
time for it any longer, we would let another contributor pick the task up.
> Implement IgniteMultimap data structures
>
>
> Key: IGNITE-640
> URL: https://issues.apache.org/jira/browse/IGNITE-640
> Project: Ignite
> Issue Type: Sub-task
> Components: data structures
>Reporter: Dmitriy Setrakyan
>Assignee: Amir Akhmedov
>Priority: Major
> Fix For: 2.9
>
>
> We need to add {{IgniteMultimap}} data structure in addition to other data
> structures provided by Ignite. {{IgniteMultiMap}} should have similar API to
> {{java.util.Map}} class in JDK, but support the semantics of multiple values
> per key, similar to [Guava
> Multimap|http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/collect/Multimap.html].
>
> However, unlike in Guava, our multi-map should work with Lists, not
> Collections. Lists should make it possible to support the following methods:
> {code}
> // Gets value at a certain index for a key.
> V get(K, index);
> // Gets all values for a collection of keys at a certain index.
> Map getAll(Collection, index);
> // Gets values for specified indexes for a key.
> List get(K, Iterable indexes);
> // Gets all values for a collection of keys at specified indexes.
> Map> getAll(Collection, Iterable indexes);
> // Gets values for specified range of indexes, between min and max.
> List get(K, int min, int max);
> // Gets all values for a collection of keys for a specified index range,
> between min and max.
> Map> getAll(Collection, int min, int max);
> // Gets all values for a specific key.
> List get(K);
> // Gets all values for a collection of keys.
> Map> getAll(Collection);
> // Iterate through all elements with a certain index.
> Iterator> iterate(int idx);
> // Do we need this?
> Collection> get(K, IgniteBiPredicate)
> {code}
> Multimap should also support colocated and non-colocated modes, similar to
> [IgniteQueue|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/IgniteQueue.java]
> and its implementation,
> [GridAtomicCacheQueueImpl|https://github.com/apache/incubator-ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/datastructures/GridAtomicCacheQueueImpl.java].
> h2. Design Details
> The most natural way to implement such map, would be to store every value
> under a separate key in an Ignite cache. For example, let's say that we have
> a key {{K}} with multiple values: {{V0, V1, V2, ...}}. Then the cache should
> end up with the following values {{K0, V0}}, {{K1, V1}}, {{K2, V2}}, etc.
> This means that we need to wrap user key into our own, internal key, which
> will also have {{index}} field.
> Also note that we need to collocate all the values for the same key on the
> same node, which means that we need to define user key K as the affinity key,
> like so:
> {code}
> class MultiKey {
> @CacheAffinityMapped
> private K key;
> int index;
> }
> {code}
> Look ups of values at specific indexes becomes very simple. Just attach a
> specific index to a key and do a cache lookup. Look ups for all values for a
> key should work as following:
> {code}
> MultiKey key;
> V v = null;
> int index = 0;
> List res = new LinkedList<>();
> do {
> v = cache.get(MultiKey(K, index));
> if (v != null)
> res.add(v);
> index++;
> }
> while (v != null);
> return res;
> {code}
> We could also use batching for performance reason. In this case the batch
> size should be configurable.
> {code}
> int index = 0;
> List res = new LinkedList<>();
> while (true) {
> List batch = new ArrayList<>(batchSize);
> // Populate batch.
> for (; index < batchSize; index++)
> batch.add(new MultiKey(K, index % batchSize);
> Map batchRes = cache.getAll(batch);
> // Potentially need to properly sort values, based on the key order,
> // if the returning map does not do it automatically.
> res.addAll(batchRes.values());
> if (res.size() < batch.size())
> break;
> }
> return res;
> {code}
> h2. Evictions
> Evictions in the {{IgniteMultiMap}} should have 2 levels: maximum number of
> keys, and maximum number of values for a key. The maximum number of keys
> should be controlled by Ignite standard eviction policy. The maximum number
> of values for a key should be controlled by the implementation of the
> multi-map. Either eviction parameter should be configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-532) Implement IgniteAkkaStreamer to stream data from Akka actors.
[
https://issues.apache.org/jira/browse/IGNITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis A. Magda updated IGNITE-532:
--
Component/s: integrations
> Implement IgniteAkkaStreamer to stream data from Akka actors.
> -
>
> Key: IGNITE-532
> URL: https://issues.apache.org/jira/browse/IGNITE-532
> Project: Ignite
> Issue Type: Sub-task
> Components: integrations, streaming
>Reporter: Dmitriy Setrakyan
>Assignee: Nikolay Izhikov
>Priority: Major
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Akka|http://akka.io/] for more information. Given that Akka is a Scala
> frameworks, this streamer should be available in Scala.
> We should create {{IgniteAkkaStreamer}} which will consume messages from Akka
> Actors and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert data from Akka to Ignite using an optional pluggable converter. If
> not provided, then we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-536) Implement IgniteKinesisStreamer to stream data from Amazon Kinesis service
[
https://issues.apache.org/jira/browse/IGNITE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis A. Magda updated IGNITE-536:
--
Component/s: integrations
> Implement IgniteKinesisStreamer to stream data from Amazon Kinesis service
> --
>
> Key: IGNITE-536
> URL: https://issues.apache.org/jira/browse/IGNITE-536
> Project: Ignite
> Issue Type: Sub-task
> Components: integrations, streaming
>Reporter: Dmitriy Setrakyan
>Priority: Major
>
> We have {{IgniteDataStreamer}} which is used to load data into Ignite under
> high load. It was previously named {{IgniteDataLoader}}, see ticket
> IGNITE-394.
> See [Amazon Kinesis|http://aws.amazon.com/kinesis/] site for more info.
> We should create {{IgniteKinesisStreamer}} which will consume messages from
> Amazon Kinesis and stream them into Ignite caches.
> More details to follow, but to the least we should be able to:
> * Convert Kinesis messages to Ignite data using an optional pluggable
> converter. If not provided, we should have some default mechanism.
> * Specify the cache name for the Ignite cache to load data into.
> * Specify other flags available on {{IgniteDataStreamer}} class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-949) Add Python API for Ignite RDD
[ https://issues.apache.org/jira/browse/IGNITE-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-949: -- Component/s: integrations > Add Python API for Ignite RDD > - > > Key: IGNITE-949 > URL: https://issues.apache.org/jira/browse/IGNITE-949 > Project: Ignite > Issue Type: Task > Components: cache, integrations >Reporter: Alexey Goncharuk >Priority: Major > > Should be close to the Java version: > https://apacheignite.readme.io/docs/ignitecontext--igniterdd -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-3131) Connectors for Apache Apex
[ https://issues.apache.org/jira/browse/IGNITE-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis A. Magda updated IGNITE-3131: --- Component/s: integrations > Connectors for Apache Apex > -- > > Key: IGNITE-3131 > URL: https://issues.apache.org/jira/browse/IGNITE-3131 > Project: Ignite > Issue Type: Improvement > Components: integrations >Reporter: Dmitriy Setrakyan >Assignee: Vladisav Jelisavcic >Priority: Major > > Apache Apex is a unified stream and batch processing platform: > http://apex.apache.org/ > http://apex.apache.org/docs.html > Apex has a large library of connectors for integration with many other > ecosystem projects. It would be great to have support for Ignite. Here are > some examples: > https://github.com/apache/incubator-apex-malhar/tree/master/contrib/src/main/java/com/datatorrent/contrib/geode > https://github.com/apache/incubator-apex-malhar/tree/master/contrib/src/main/java/com/datatorrent/contrib/cassandra > https://github.com/apache/incubator-apex-malhar/tree/master/contrib/src/main/java/com/datatorrent/contrib/nifi > The logical place for the implementation would the the Malhar repository, but > approach and development should be driven by the Ignite community. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12481) .NET: NuGet verification script does not handle multi-digit version parts
[
https://issues.apache.org/jira/browse/IGNITE-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12481:
Ignite Flags: (was: Docs Required,Release Notes Required)
> .NET: NuGet verification script does not handle multi-digit version parts
> -
>
> Key: IGNITE-12481
> URL: https://issues.apache.org/jira/browse/IGNITE-12481
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.9
>
>
> The following regex in verify-nuget.ps1 does not support multi-digit versions
> like 8.7.99
> {code}
> $packageId = $_.Name -replace '(.*?)\.\d\.\d\.\d\.nupkg', '$1'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12481) .NET: NuGet verification script does not handle multi-digit version parts
[
https://issues.apache.org/jira/browse/IGNITE-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12481:
Labels: .NET (was: )
> .NET: NuGet verification script does not handle multi-digit version parts
> -
>
> Key: IGNITE-12481
> URL: https://issues.apache.org/jira/browse/IGNITE-12481
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.9
>
>
> The following regex in verify-nuget.ps1 does not support multi-digit versions
> like 8.7.99
> {code}
> $packageId = $_.Name -replace '(.*?)\.\d\.\d\.\d\.nupkg', '$1'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12481) .NET: NuGet verification script does not handle multi-digit version parts
[
https://issues.apache.org/jira/browse/IGNITE-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001024#comment-17001024
]
Pavel Tupitsyn commented on IGNITE-12481:
-
Merged to master: 6facbc7ffe25ee62727aed84cf3fd9e97cb35984
> .NET: NuGet verification script does not handle multi-digit version parts
> -
>
> Key: IGNITE-12481
> URL: https://issues.apache.org/jira/browse/IGNITE-12481
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.9
>
>
> The following regex in verify-nuget.ps1 does not support multi-digit versions
> like 8.7.99
> {code}
> $packageId = $_.Name -replace '(.*?)\.\d\.\d\.\d\.nupkg', '$1'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-12481) .NET: NuGet verification script does not handle multi-digit version parts
[
https://issues.apache.org/jira/browse/IGNITE-12481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-12481.
-
Resolution: Fixed
> .NET: NuGet verification script does not handle multi-digit version parts
> -
>
> Key: IGNITE-12481
> URL: https://issues.apache.org/jira/browse/IGNITE-12481
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Fix For: 2.9
>
>
> The following regex in verify-nuget.ps1 does not support multi-digit versions
> like 8.7.99
> {code}
> $packageId = $_.Name -replace '(.*?)\.\d\.\d\.\d\.nupkg', '$1'
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12481) .NET: NuGet verification script does not handle multi-digit version parts
Pavel Tupitsyn created IGNITE-12481:
---
Summary: .NET: NuGet verification script does not handle
multi-digit version parts
Key: IGNITE-12481
URL: https://issues.apache.org/jira/browse/IGNITE-12481
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.9
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: 2.9
The following regex in verify-nuget.ps1 does not support multi-digit versions
like 8.7.99
{code}
$packageId = $_.Name -replace '(.*?)\.\d\.\d\.\d\.nupkg', '$1'
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12474) Fix boost compatibility for cpp thin-client-test.
[ https://issues.apache.org/jira/browse/IGNITE-12474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001018#comment-17001018 ] Stanilovsky Evgeny commented on IGNITE-12474: - [~isapego] check it plz. > Fix boost compatibility for cpp thin-client-test. > - > > Key: IGNITE-12474 > URL: https://issues.apache.org/jira/browse/IGNITE-12474 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Current teamcity_boost implementation leads to errors like: > "src/teamcity/teamcity_boost.cpp:22:10: fatal error: > boost/test/unit_test_suite_impl.hpp: No such file or catalog. > #include " > dev list discussion [1] > [1] > http://apache-ignite-developers.2346864.n4.nabble.com/Can-t-run-CPP-tests-locally-on-linux-machine-td29597.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12474) Fix boost compatibility for cpp thin-client-test.
[
https://issues.apache.org/jira/browse/IGNITE-12474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001017#comment-17001017
]
Ignite TC Bot commented on IGNITE-12474:
{panel:title=Branch: [pull/7171/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=4860128buildTypeId=IgniteTests24Java8_RunAll]
> Fix boost compatibility for cpp thin-client-test.
> -
>
> Key: IGNITE-12474
> URL: https://issues.apache.org/jira/browse/IGNITE-12474
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
>Affects Versions: 2.7.6
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Current teamcity_boost implementation leads to errors like:
> "src/teamcity/teamcity_boost.cpp:22:10: fatal error:
> boost/test/unit_test_suite_impl.hpp: No such file or catalog.
> #include "
> dev list discussion [1]
> [1]
> http://apache-ignite-developers.2346864.n4.nabble.com/Can-t-run-CPP-tests-locally-on-linux-machine-td29597.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12480) Add BinaryFieldExtractionSelfTest to the Binary Objects test suite
Denis Mekhanikov created IGNITE-12480: - Summary: Add BinaryFieldExtractionSelfTest to the Binary Objects test suite Key: IGNITE-12480 URL: https://issues.apache.org/jira/browse/IGNITE-12480 Project: Ignite Issue Type: Test Components: binary Reporter: Denis Mekhanikov Assignee: Denis Mekhanikov Fix For: 2.8 BinaryFieldExtractionSelfTest is not run on TeamCity because it's not included into any test suite. It should be added into IgniteBinaryObjectsTestSuite -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12120) Change log level in GridCacheWritebehindStore
[
https://issues.apache.org/jira/browse/IGNITE-12120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-12120:
-
Reviewer: Ilya Kasnacheev
> Change log level in GridCacheWritebehindStore
> -
>
> Key: IGNITE-12120
> URL: https://issues.apache.org/jira/browse/IGNITE-12120
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.5
>Reporter: Sunny Chan
>Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the
> [GridCacheWriteBehindStore|https://github.com/apache/ignite/blob/7e73098d4d6e3d5f78326cb11dac7e083a2312dd/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/store/GridCacheWriteBehindStore.java#L893],
> when the updateStore failed to write to underlying store, it logs this as
> error:
> {{LT.error(log, e, "Unable to update underlying store: " + store);}}
> After this line logged the error, it would return false so that it would
> retry the store (by returning false).
> While later on in the updatStore function, when the writeCache overflows, it
> would log this:
> {{log.warning("Failed to update store (value will be lost as current buffer
> size is greater " + …}}
> then it will remove the failed entry.
> I think the severity of the log messages is not right, as the fail update
> would still be retried.
> So I propose to change the log severity level so that the first one would be
> a warn, and second one would be error
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-7792) IgniteDatabaseSharedManager refactoring
[
https://issues.apache.org/jira/browse/IGNITE-7792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stanilovsky Evgeny reassigned IGNITE-7792:
--
Assignee: Stanilovsky Evgeny
> IgniteDatabaseSharedManager refactoring
> ---
>
> Key: IGNITE-7792
> URL: https://issues.apache.org/jira/browse/IGNITE-7792
> Project: Ignite
> Issue Type: Task
> Components: cache
>Reporter: Igor Seliverstov
>Assignee: Stanilovsky Evgeny
>Priority: Minor
>
> Currently there is no mapping of cacheId to page memory which prevents adding
> custom persistent structures
> ({{GridCacheDatabaseSharedManager.WriteCheckpointPages#run}}).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12479) All binary types are registered twice
Denis Mekhanikov created IGNITE-12479:
-
Summary: All binary types are registered twice
Key: IGNITE-12479
URL: https://issues.apache.org/jira/browse/IGNITE-12479
Project: Ignite
Issue Type: Bug
Components: binary
Reporter: Denis Mekhanikov
Assignee: Denis Mekhanikov
Fix For: 2.8
When a POJO is put into a cache, its binary type is registered twice during
marshalling.
Example:
{code:java}
public class MetadataRegistrationExample {
public static void main(String[] args) {
Ignite ignite = Ignition.start("config/ignite.xml");
Person p = new Person("Denis");
ignite.getOrCreateCache("cache").put(1, p);
}
static class Person {
private String name;
public Person(String name) {
this.name = name;
}
}
}
{code}
Here is the generated debug log from the package
{noformat}
[23:31:14,020][DEBUG][main][CacheObjectBinaryProcessorImpl] Requesting metadata
update [typeId=-1210012928,
typeName=binary.NestedObjectMarshallingExample$Person, changedSchemas=[],
holder=null, fut=MetadataUpdateResultFuture [key=SyncKey [typeId=-1210012928,
ver=0]]]
[23:31:14,023][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Received MetadataUpdateProposedListener [typeId=-1210012928,
typeName=binary.NestedObjectMarshallingExample$Person, pendingVer=0,
acceptedVer=0, schemasCnt=0]
[23:31:14,024][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Versions are stamped on coordinator [typeId=-1210012928, changedSchemas=[],
pendingVer=1, acceptedVer=0]
[23:31:14,024][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Updated metadata on originating node: [typeId=-1210012928, pendingVer=1,
acceptedVer=0]
[23:31:14,025][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Received MetadataUpdateAcceptedMessage MetadataUpdateAcceptedMessage
[id=599e0a86c61-183a790b-7038-4dd5-b99d-89f1483e3635, typeId=-1210012928,
acceptedVer=1, duplicated=false]
[23:31:14,025][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Completing future MetadataUpdateResultFuture [key=SyncKey [typeId=-1210012928,
ver=1]] for [typeId=-1210012928, pendingVer=1, acceptedVer=1]
[23:31:14,026][DEBUG][main][CacheObjectBinaryProcessorImpl] Completed metadata
update [typeId=-1210012928,
typeName=binary.NestedObjectMarshallingExample$Person, waitTime=4ms,
fut=MetadataUpdateResultFuture [key=SyncKey [typeId=-1210012928, ver=1]],
tx=null]
[23:31:14,027][DEBUG][main][CacheObjectBinaryProcessorImpl] Requesting metadata
update [typeId=-1210012928,
typeName=binary.NestedObjectMarshallingExample$Person,
changedSchemas=[1975878747], holder=[typeId=-1210012928, pendingVer=1,
acceptedVer=1], fut=MetadataUpdateResultFuture [key=SyncKey
[typeId=-1210012928, ver=0]]]
[23:31:14,027][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Received MetadataUpdateProposedListener [typeId=-1210012928,
typeName=binary.NestedObjectMarshallingExample$Person, pendingVer=0,
acceptedVer=0, schemasCnt=1]
[23:31:14,028][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Versions are stamped on coordinator [typeId=-1210012928,
changedSchemas=[1975878747], pendingVer=2, acceptedVer=1]
[23:31:14,028][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Updated metadata on originating node: [typeId=-1210012928, pendingVer=2,
acceptedVer=1]
[23:31:14,028][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Received MetadataUpdateAcceptedMessage MetadataUpdateAcceptedMessage
[id=d99e0a86c61-183a790b-7038-4dd5-b99d-89f1483e3635, typeId=-1210012928,
acceptedVer=2, duplicated=false]
[23:31:14,028][DEBUG][disco-notifier-worker-#41][CacheObjectBinaryProcessorImpl]
Completing future MetadataUpdateResultFuture [key=SyncKey [typeId=-1210012928,
ver=2]] for [typeId=-1210012928, pendingVer=2, acceptedVer=2]
[23:31:14,029][DEBUG][main][CacheObjectBinaryProcessorImpl] Completed metadata
update [typeId=-1210012928,
typeName=binary.NestedObjectMarshallingExample$Person, waitTime=1ms,
fut=MetadataUpdateResultFuture [key=SyncKey [typeId=-1210012928, ver=2]],
tx=null]
{noformat}
You can see, that a type is registered twice. First it's registered without any
fields, and only the second time the type is registered properly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12478) Add long running operation timeout to MXBean for manipulate in run-time
Kirill Tkalenko created IGNITE-12478:
Summary: Add long running operation timeout to MXBean for
manipulate in run-time
Key: IGNITE-12478
URL: https://issues.apache.org/jira/browse/IGNITE-12478
Project: Ignite
Issue Type: Improvement
Reporter: Kirill Tkalenko
Assignee: Kirill Tkalenko
Fix For: 2.8
Previously we can change the timeout only through property
({{IGNITE_LONG_OPERATIONS_DUMP_TIMEOUT}} default 60_000), but in a real
environment, we do not want to stop cluster (or node) for modify this property.
We should have a MBean's property, which allow to fluent in run-time behavior
of printing LRT/LRF (like a property
{{SqlQueryMXBeanImpl#setLongQueryWarningTimeout}} which printing long running
queries).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12470: - Priority: Blocker (was: Major) > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Sergei Ryzhov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12470: - Fix Version/s: 2.8 > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Sergei Ryzhov >Priority: Major > Labels: newbie > Fix For: 2.8, 2.9 > > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12301) Free-lists system view
[
https://issues.apache.org/jira/browse/IGNITE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000870#comment-17000870
]
Ignite TC Bot commented on IGNITE-12301:
{panel:title=Branch: [pull/6991/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=4860012buildTypeId=IgniteTests24Java8_RunAll]
> Free-lists system view
> --
>
> Key: IGNITE-12301
> URL: https://issues.apache.org/jira/browse/IGNITE-12301
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: IEP-35
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> Implement a system view for free-lists monitoring.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12477) Slow test in Queries 1 test suite
[ https://issues.apache.org/jira/browse/IGNITE-12477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-12477: --- Assignee: Ivan Pavlukhin > Slow test in Queries 1 test suite > - > > Key: IGNITE-12477 > URL: https://issues.apache.org/jira/browse/IGNITE-12477 > Project: Ignite > Issue Type: Task >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > > "Queries 1" suite execution time can be optimized. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12476) Slow test in Continuous Query 1 test suite
[ https://issues.apache.org/jira/browse/IGNITE-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-12476: --- Assignee: Ivan Pavlukhin > Slow test in Continuous Query 1 test suite > -- > > Key: IGNITE-12476 > URL: https://issues.apache.org/jira/browse/IGNITE-12476 > Project: Ignite > Issue Type: Task >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > > "Continuous Query 1" suite execution time can be optimized. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-9913) Prevent data updates blocking in case of backup BLT server node leave
[ https://issues.apache.org/jira/browse/IGNITE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000857#comment-17000857 ] Anton Vinogradov commented on IGNITE-9913: -- Merged to ignite-2.8 branch. > Prevent data updates blocking in case of backup BLT server node leave > - > > Key: IGNITE-9913 > URL: https://issues.apache.org/jira/browse/IGNITE-9913 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ivan Rakov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.8, 2.9 > > Attachments: 9913_yardstick.png, master_yardstick.png > > Time Spent: 10h 40m > Remaining Estimate: 0h > > Ignite cluster performs distributed partition map exchange when any server > node leaves or joins the topology. > Distributed PME blocks all updates and may take a long time. If all > partitions are assigned according to the baseline topology and server node > leaves, there's no actual need to perform distributed PME: every cluster node > is able to recalculate new affinity assigments and partition states locally. > If we'll implement such lightweight PME and handle mapping and lock requests > on new topology version correctly, updates won't be stopped (except updates > of partitions that lost their primary copy). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-9913) Prevent data updates blocking in case of backup BLT server node leave
[ https://issues.apache.org/jira/browse/IGNITE-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-9913: - Fix Version/s: 2.8 > Prevent data updates blocking in case of backup BLT server node leave > - > > Key: IGNITE-9913 > URL: https://issues.apache.org/jira/browse/IGNITE-9913 > Project: Ignite > Issue Type: Improvement > Components: general >Reporter: Ivan Rakov >Assignee: Anton Vinogradov >Priority: Major > Fix For: 2.8, 2.9 > > Attachments: 9913_yardstick.png, master_yardstick.png > > Time Spent: 10.5h > Remaining Estimate: 0h > > Ignite cluster performs distributed partition map exchange when any server > node leaves or joins the topology. > Distributed PME blocks all updates and may take a long time. If all > partitions are assigned according to the baseline topology and server node > leaves, there's no actual need to perform distributed PME: every cluster node > is able to recalculate new affinity assigments and partition states locally. > If we'll implement such lightweight PME and handle mapping and lock requests > on new topology version correctly, updates won't be stopped (except updates > of partitions that lost their primary copy). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12301) Free-lists system view
[ https://issues.apache.org/jira/browse/IGNITE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000856#comment-17000856 ] Nikolay Izhikov commented on IGNITE-12301: -- LGTM > Free-lists system view > -- > > Key: IGNITE-12301 > URL: https://issues.apache.org/jira/browse/IGNITE-12301 > Project: Ignite > Issue Type: Improvement >Reporter: Aleksey Plekhanov >Assignee: Aleksey Plekhanov >Priority: Major > Labels: IEP-35 > Time Spent: 1.5h > Remaining Estimate: 0h > > Implement a system view for free-lists monitoring. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12477) Slow test in Queries 1 test suite
Ivan Pavlukhin created IGNITE-12477: --- Summary: Slow test in Queries 1 test suite Key: IGNITE-12477 URL: https://issues.apache.org/jira/browse/IGNITE-12477 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin "Queries 1" suite execution time can be optimized. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12476) Slow test in Continuous Query 1 test suite
Ivan Pavlukhin created IGNITE-12476: --- Summary: Slow test in Continuous Query 1 test suite Key: IGNITE-12476 URL: https://issues.apache.org/jira/browse/IGNITE-12476 Project: Ignite Issue Type: Task Reporter: Ivan Pavlukhin "Continuous Query 1" suite execution time can be optimized. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-12448) Calcite integration. Communication protocol.
[ https://issues.apache.org/jira/browse/IGNITE-12448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov reassigned IGNITE-12448: - Assignee: Igor Seliverstov > Calcite integration. Communication protocol. > > > Key: IGNITE-12448 > URL: https://issues.apache.org/jira/browse/IGNITE-12448 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Igor Seliverstov >Assignee: Igor Seliverstov >Priority: Major > > We need to introduce a communication protocol between query fragments in > scope of query execution. > * Protocol should have Push semantics with back pressure ability > * Protocol have to provide ordering guaranties - the data batches processed > in same order they sent to remote node. > * Protocol have to provide delivery guaranties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-11939) IgnitePdsTxHistoricalRebalancingTest.testTopologyChangesWithConstantLoad test failure
[
https://issues.apache.org/jira/browse/IGNITE-11939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirza Aliev reassigned IGNITE-11939:
Assignee: Mirza Aliev
> IgnitePdsTxHistoricalRebalancingTest.testTopologyChangesWithConstantLoad
> test failure
> --
>
> Key: IGNITE-11939
> URL: https://issues.apache.org/jira/browse/IGNITE-11939
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexey Scherbakov
>Assignee: Mirza Aliev
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Caused by exception on releasing reserved segments:
> {noformat}
> [12:51:23]W: [org.apache.ignite:ignite-indexing] [2019-06-21
> 12:51:23,967][ERROR][exchange-worker-#33825%persistence.IgnitePdsTxHistoricalRebalancingTest1%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (rebalancing will be stopped)
> : GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=CacheAffinityChangeMessage
> [id=08de0ff7b61-276ac575-e4dc-4525-b24b-d0a5d1d7633d,
> topVer=AffinityTopologyVersion [topVer=7, minorTopVer=0], exc
> hId=null, partsMsg=null, exchangeNeeded=true],
> affTopVer=AffinityTopologyVersion [topVer=7, minorTopVer=1],
> super=DiscoveryEvent [evtNode=TcpDiscoveryNode
> [id=97e46568-6aa0-4a4b-864c-f05415c0,
> consistentId=persistence.IgnitePdsTxHistoricalRebalancingTest0, addrs=Arra
> yList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47500], discPort=47500,
> order=1, intOrder=1, lastExchangeTime=1561110643882, loc=false,
> ver=2.8.0#20190621-sha1:, isClient=false], topVer=7,
> nodeId8=0ff3354e, msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=15611106839
> 58]], nodeId=97e46568, evt=DISCOVERY_CUSTOM_EVT]
> [12:51:23]W: [org.apache.ignite:ignite-indexing]
> java.lang.AssertionError: cur=null, absIdx=0
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentReservationStorage.release(SegmentReservationStorage.java:55)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentAware.release(SegmentAware.java:207)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.release(FileWriteAheadLogManager.java:983)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.releaseHistoryForPreloading(GridCacheDatabaseSharedManager.java:1844)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1431)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:862)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:3079)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2928)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> java.lang.Thread.run(Thread.java:748)
> [12:51:23]W: [org.apache.ignite:ignite-indexing] [12:51:23] (err)
> Failed to notify listener:
> o.a.i.i.processors.timeout.GridTimeoutProcessor$2...@79ba1907java.lang.AssertionError:
> cur=null, absIdx=0
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentReservationStorage.release(SegmentReservationStorage.java:55)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.aware.SegmentAware.release(SegmentAware.java:207)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
> org.apache.ignite.internal.processors.cache.persistence.wal.FileWriteAheadLogManager.release(FileWriteAheadLogManager.java:983)
> [12:51:23]W: [org.apache.ignite:ignite-indexing]at
>
[jira] [Updated] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters
[ https://issues.apache.org/jira/browse/IGNITE-12193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-12193: - Description: Implement metrics counters related to the cache group: * rebalancingPartitionsLeft long metric * rebalancingReceivedKeys long metric * rebalancingReceivedBytes long metric * rebalancingStartTime long metric * rebalancingFinishTime long metric * rebalancingLastCancelledTime long metric was: Implement metrics counters related to the cache group: * rebalancingPartitionsLeft long metric * rebalancingReceivedKeys long metric * rebalancingReceivedBytes long metric * rebalancingStartTime long metric * rebalancingFinishTime long metric > [Phase-1] Rebalancing cache group keys metric counters > -- > > Key: IGNITE-12193 > URL: https://issues.apache.org/jira/browse/IGNITE-12193 > Project: Ignite > Issue Type: Sub-task >Reporter: Maxim Muzafarov >Assignee: Nikolai Kulagin >Priority: Critical > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 2h > Remaining Estimate: 0h > > Implement metrics counters related to the cache group: > * rebalancingPartitionsLeft long metric > * rebalancingReceivedKeys long metric > * rebalancingReceivedBytes long metric > * rebalancingStartTime long metric > * rebalancingFinishTime long metric > * rebalancingLastCancelledTime long metric -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12183) Rebalancing process metrics for cache groups
[
https://issues.apache.org/jira/browse/IGNITE-12183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-12183:
-
Description:
h3. Intro
Currently, some of the Apache Ignite rebalance process metrics are not working
well enough. For instance, `EstimatedRebalancingKeys` keys time to time returns
`-1` value due to a bug, or `rebalanceKeysReceived` metric treated as
CacheMetric in fact calculated for the whole cache group (e.g. historical
rebalance, see IGNITE-11330 and code block comment below).
All the rebalance process metrics must be re-worked.
{code:java}
/**
* Update rebalancing metrics.
*/
private void updateGroupMetrics() {
// TODO: IGNITE-11330: Update metrics for touched cache only.
// Due to historical rebalancing "EstimatedRebalancingKeys" metric is
currently calculated for the whole cache
// group (by partition counters), so "RebalancedKeys" and
"RebalancingKeysRate" is calculated in the same way.
for (GridCacheContext cctx0 : grp.caches()) {
if (cctx0.statisticsEnabled())
cctx0.cache().metrics0().onRebalanceKeyReceived();
}
}
{code}
h3. What we have
_CacheMetrics_ - statistics must be enabled to see these metrics.
* getRebalancedKeys
* getKeysToRebalanceLeft
* getEstimatedRebalancingKeys
* getEstimatedRebalancingFinishTime
* getRebalancingStartTime
* getRebalanceClearingPartitionsLeft
* getRebalancingKeysRate
* getRebalancingBytesRate
h3. What to do
All such metrics (or their analogue) must be available for the
_CacheGroupMetrics_. I'd suggest to do the following:
# Phase-1
#* rebalancingPartitionsLeft long metric
#* rebalancingReceivedKeys long metric
#* rebalancingReceivedBytes long metric
#* rebalancingStartTime long metric
#* rebalancingFinishTime long metric
#* rebalancingLastCancelledTime long metric
# Phase-2
#* rebalancingExpectedKeys long metric
#* rebalancingExpectedBytes long metric
#* rebalancingEvictedPartitionsLeft long metric
# Phase-3 (statistics must be enabled)
#* rebalancingKeysRate HitRate metric
#* rebalancingBytesRate HitRate metric
# Phase-4
#* Mark rebalancing _CacheMetrics_ deprecated and remove from metrics framework
IGNITE-11961.
was:
h3. Intro
Currently, some of the Apache Ignite rebalance process metrics are not working
well enough. For instance, `EstimatedRebalancingKeys` keys time to time returns
`-1` value due to a bug, or `rebalanceKeysReceived` metric treated as
CacheMetric in fact calculated for the whole cache group (e.g. historical
rebalance, see IGNITE-11330 and code block comment below).
All the rebalance process metrics must be re-worked.
{code:java}
/**
* Update rebalancing metrics.
*/
private void updateGroupMetrics() {
// TODO: IGNITE-11330: Update metrics for touched cache only.
// Due to historical rebalancing "EstimatedRebalancingKeys" metric is
currently calculated for the whole cache
// group (by partition counters), so "RebalancedKeys" and
"RebalancingKeysRate" is calculated in the same way.
for (GridCacheContext cctx0 : grp.caches()) {
if (cctx0.statisticsEnabled())
cctx0.cache().metrics0().onRebalanceKeyReceived();
}
}
{code}
h3. What we have
_CacheMetrics_ - statistics must be enabled to see these metrics.
* getRebalancedKeys
* getKeysToRebalanceLeft
* getEstimatedRebalancingKeys
* getEstimatedRebalancingFinishTime
* getRebalancingStartTime
* getRebalanceClearingPartitionsLeft
* getRebalancingKeysRate
* getRebalancingBytesRate
h3. What to do
All such metrics (or their analogue) must be available for the
_CacheGroupMetrics_. I'd suggest to do the following:
# Phase-1
#* rebalancingPartitionsLeft long metric
#* rebalancingReceivedKeys long metric
#* rebalancingReceivedBytes long metric
#* rebalancingStartTime long metric
#* rebalancingFinishTime long metric
# Phase-2
#* rebalancingExpectedKeys long metric
#* rebalancingExpectedBytes long metric
#* rebalancingEvictedPartitionsLeft long metric
# Phase-3 (statistics must be enabled)
#* rebalancingKeysRate HitRate metric
#* rebalancingBytesRate HitRate metric
# Phase-4
#* Mark rebalancing _CacheMetrics_ deprecated and remove from metrics framework
IGNITE-11961.
> Rebalancing process metrics for cache groups
>
>
> Key: IGNITE-12183
> URL: https://issues.apache.org/jira/browse/IGNITE-12183
> Project: Ignite
> Issue Type: Improvement
>Reporter: Aleksandr Brazhnikov
>Priority: Major
> Labels: IEP-35
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h3. Intro
> Currently, some of the Apache Ignite rebalance process metrics are not
> working well enough. For instance, `EstimatedRebalancingKeys` keys time to
> time returns `-1` value due to a bug,
[jira] [Commented] (IGNITE-12442) Fix unnecessary synchronized on PagesCache#add.
[ https://issues.apache.org/jira/browse/IGNITE-12442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000829#comment-17000829 ] Aleksey Plekhanov commented on IGNITE-12442: [~zstan], looks good to me. Merged to master. Thanks for your contribution! > Fix unnecessary synchronized on PagesCache#add. > --- > > Key: IGNITE-12442 > URL: https://issues.apache.org/jira/browse/IGNITE-12442 > Project: Ignite > Issue Type: Improvement > Components: data structures >Affects Versions: 2.7.6 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Fix For: 2.9 > > Time Spent: 40m > Remaining Estimate: 0h > > After [IGNITE-6930|https://issues.apache.org/jira/browse/IGNITE-6930] was > implemented, there are some synchronization extra usage found. > 1. > org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.PagesCache#add > 2. > org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.PagesCache#emptyFlushCnt > hope need to fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense
[ https://issues.apache.org/jira/browse/IGNITE-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-5097: --- Fix Version/s: 3.0 > BinaryMarshaller should write ints in "varint" encoding where it makes sense > > > Key: IGNITE-5097 > URL: https://issues.apache.org/jira/browse/IGNITE-5097 > Project: Ignite > Issue Type: Task > Components: binary >Affects Versions: 2.0 >Reporter: Vladimir Ozerov >Assignee: Vyacheslav Daradur >Priority: Major > Labels: iep-2, performance > Fix For: 3.0 > > > There are a lot of places in the code where we write integers for some > special purposes. Quite often their value will be vary small, so that > applying "varint" format could save a lot of space at the cost of very low > additional CPU overhead. > Specifically: > 1) Array/collection/map lengths > 2) BigDecimal's (usually will save ~6 bytes) > 3) Strings > 4) Enum ordinals -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12475) TDE - Phase-2. CLI process management
Amelchev Nikita created IGNITE-12475:
Summary: TDE - Phase-2. CLI process management
Key: IGNITE-12475
URL: https://issues.apache.org/jira/browse/IGNITE-12475
Project: Ignite
Issue Type: Sub-task
Reporter: Amelchev Nikita
Assignee: Amelchev Nikita
Provide the ability to manage the process from CLI:
{noformat}
# Starts master key rotation.
control.sh --encryption change_master_key newMasterKeyName
# Displays cluster's current master key name.
control.sh --encryption get_master_key
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12049) Add user attributes to thin clients
[
https://issues.apache.org/jira/browse/IGNITE-12049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000765#comment-17000765
]
Ignite TC Bot commented on IGNITE-12049:
{panel:title=Branch: [pull/6796/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=4854414buildTypeId=IgniteTests24Java8_RunAll]
> Add user attributes to thin clients
> ---
>
> Key: IGNITE-12049
> URL: https://issues.apache.org/jira/browse/IGNITE-12049
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ryabov Dmitrii
>Assignee: Ryabov Dmitrii
>Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Add user attributes to thin clients (like node attributes for server nodes).
> Make sure that custom authenticators can use these attributes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12462) JDBC thin: add timeouts as the parameters for connection string
[ https://issues.apache.org/jira/browse/IGNITE-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-12462: -- Ignite Flags: Docs Required (was: Docs Required,Release Notes Required) Release Note: JDBC thin client supports 'connectionTimeout' and 'queryTimout' properties. > JDBC thin: add timeouts as the parameters for connection string > --- > > Key: IGNITE-12462 > URL: https://issues.apache.org/jira/browse/IGNITE-12462 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > We've added two new timeouts ([1], [2]) but they're available from java code > only and both should be add as the connection string parameters. > 1. https://issues.apache.org/jira/browse/IGNITE-5438 > 2. https://issues.apache.org/jira/browse/IGNITE-5234 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12462) JDBC thin: add timeouts as the parameters for connection string
[ https://issues.apache.org/jira/browse/IGNITE-12462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000723#comment-17000723 ] Ivan Pavlukhin commented on IGNITE-12462: - [~amashenkov], LGTM. > JDBC thin: add timeouts as the parameters for connection string > --- > > Key: IGNITE-12462 > URL: https://issues.apache.org/jira/browse/IGNITE-12462 > Project: Ignite > Issue Type: Task > Components: thin client >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > We've added two new timeouts ([1], [2]) but they're available from java code > only and both should be add as the connection string parameters. > 1. https://issues.apache.org/jira/browse/IGNITE-5438 > 2. https://issues.apache.org/jira/browse/IGNITE-5234 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11705) Jdbc Thin: add ability to control affinity cache size.
[ https://issues.apache.org/jira/browse/IGNITE-11705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000722#comment-17000722 ] Ivan Pavlukhin commented on IGNITE-11705: - [~amashenkov], LGTM. > Jdbc Thin: add ability to control affinity cache size. > -- > > Key: IGNITE-11705 > URL: https://issues.apache.org/jira/browse/IGNITE-11705 > Project: Ignite > Issue Type: Task > Components: jdbc >Reporter: Alexander Lapin >Assignee: Andrey Mashenkov >Priority: Major > Labels: iep-24 > Fix For: 2.9 > > Time Spent: 10m > Remaining Estimate: 0h > > Within AffinityCache there are two properties DISTRIBUTIONS_CACHE_LIMIT and > SQL_CACHE_LIMIT that are hard coded. We should add an ability to control > given parameters within some sort of configuration. IgniteSystemProperties is > not an option however. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12473) .NET: ClientServerCompatibilityTest fails on some agents because of Maven error
[
https://issues.apache.org/jira/browse/IGNITE-12473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn resolved IGNITE-12473.
-
Resolution: Fixed
> .NET: ClientServerCompatibilityTest fails on some agents because of Maven
> error
> ---
>
> Key: IGNITE-12473
> URL: https://issues.apache.org/jira/browse/IGNITE-12473
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.8
>
>
> We should set language version explicitly in the pom.xml
> {code}
> [00:04:21][Apache.Ignite.Core.Tests.exe] >>> 35584 OUT: [ERROR]
> COMPILATION ERROR :
> [00:04:21][Apache.Ignite.Core.Tests.exe] >>> 35584 OUT: [INFO]
> -
> [00:04:21][Apache.Ignite.Core.Tests.exe] >>> 35584 OUT: [ERROR] Source
> option 1.5 is no longer supported. Use 1.6 or later.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12473) .NET: ClientServerCompatibilityTest fails on some agents because of Maven error
[
https://issues.apache.org/jira/browse/IGNITE-12473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000712#comment-17000712
]
Pavel Tupitsyn commented on IGNITE-12473:
-
Merged to master: a2041cee31c7859ab8baaffeaad52f0acee1f9c8
Cherry-picked to 2.8-master: 27718d9971cfa7b0d074d9d1ea8e916a694b262d
> .NET: ClientServerCompatibilityTest fails on some agents because of Maven
> error
> ---
>
> Key: IGNITE-12473
> URL: https://issues.apache.org/jira/browse/IGNITE-12473
> Project: Ignite
> Issue Type: Bug
> Components: platforms
>Affects Versions: 2.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.8
>
>
> We should set language version explicitly in the pom.xml
> {code}
> [00:04:21][Apache.Ignite.Core.Tests.exe] >>> 35584 OUT: [ERROR]
> COMPILATION ERROR :
> [00:04:21][Apache.Ignite.Core.Tests.exe] >>> 35584 OUT: [INFO]
> -
> [00:04:21][Apache.Ignite.Core.Tests.exe] >>> 35584 OUT: [ERROR] Source
> option 1.5 is no longer supported. Use 1.6 or later.
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12469) CorruptedTreeException can hold unmutable sensitive data.
[
https://issues.apache.org/jira/browse/IGNITE-12469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000710#comment-17000710
]
Ignite TC Bot commented on IGNITE-12469:
{panel:title=Branch: [pull/7163/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=4855372buildTypeId=IgniteTests24Java8_RunAll]
> CorruptedTreeException can hold unmutable sensitive data.
> -
>
> Key: IGNITE-12469
> URL: https://issues.apache.org/jira/browse/IGNITE-12469
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.7.6
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> System property IGNITE_TO_STRING_INCLUDE_SENSITIVE don`t hide sensitive data
> while CorruptedTreeException occurred.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
