[jira] [Updated] (IGNITE-13742) Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
[
https://issues.apache.org/jira/browse/IGNITE-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-13742:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Fix failed
> WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
> -
>
> Key: IGNITE-13742
> URL: https://issues.apache.org/jira/browse/IGNITE-13742
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-47
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code is to blame:
>
> {code:java}
> // Reinitialized discovery manager won't have a valid consistentId on
> creation.
> discoMgr.consistentId(ctx.pdsFolderResolver().resolveFolders().consistentId());
> {code}
> More specifically: "***.consistentId" invocation with valid consistent id
> from ANY source.
>
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5803772702668480758=testDetails]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13742) Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
[
https://issues.apache.org/jira/browse/IGNITE-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov updated IGNITE-13742:
-
Fix Version/s: 2.10
> Fix failed
> WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
> -
>
> Key: IGNITE-13742
> URL: https://issues.apache.org/jira/browse/IGNITE-13742
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-47
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code is to blame:
>
> {code:java}
> // Reinitialized discovery manager won't have a valid consistentId on
> creation.
> discoMgr.consistentId(ctx.pdsFolderResolver().resolveFolders().consistentId());
> {code}
> More specifically: "***.consistentId" invocation with valid consistent id
> from ANY source.
>
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5803772702668480758=testDetails]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13190) Core defragmentation functions
[ https://issues.apache.org/jira/browse/IGNITE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242975#comment-17242975 ] Sergey Chugunov commented on IGNITE-13190: -- [~ibessonov], I looked through the code as well, it looks good to me. As we have a green visa from TC bot, I merged it to master in commit *09d5c73c467acf13408d22ab4198bff6c2c7d229*. Thank you for this valuable contribution! > Core defragmentation functions > -- > > Key: IGNITE-13190 > URL: https://issues.apache.org/jira/browse/IGNITE-13190 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergey Chugunov >Assignee: Ivan Bessonov >Priority: Major > Labels: IEP-47 > Fix For: 2.10 > > Time Spent: 20h 50m > Remaining Estimate: 0h > > The following set of functions covering defragmentation happy-case needed: > * Initialization of defragmentation manager when node is started in > maintenance mode. > * Information about partition files is gathered by defrag mgr. > * For each partition file corresponding file of defragmented partition is > created and initialized. > * Keys are transferred from old partitions to new partitions. > * Checkpointer is aware of new partition files and flushes defragmented > memory to new partition files. > > No fault-tolerance code nor index defragmentation mappings are needed in this > task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13190) Core defragmentation functions
[ https://issues.apache.org/jira/browse/IGNITE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Chugunov updated IGNITE-13190: - Fix Version/s: 2.10 > Core defragmentation functions > -- > > Key: IGNITE-13190 > URL: https://issues.apache.org/jira/browse/IGNITE-13190 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergey Chugunov >Assignee: Ivan Bessonov >Priority: Major > Labels: IEP-47 > Fix For: 2.10 > > Time Spent: 20h 50m > Remaining Estimate: 0h > > The following set of functions covering defragmentation happy-case needed: > * Initialization of defragmentation manager when node is started in > maintenance mode. > * Information about partition files is gathered by defrag mgr. > * For each partition file corresponding file of defragmented partition is > created and initialized. > * Keys are transferred from old partitions to new partitions. > * Checkpointer is aware of new partition files and flushes defragmented > memory to new partition files. > > No fault-tolerance code nor index defragmentation mappings are needed in this > task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-13796: Description: Docs changes related to the ticket [IGNITE-13204|https://issues.apache.org/jira/browse/IGNITE-13204]. The class TcpDiscoveryKubernetesIpFinder ThinClientKubernetesAddressFinder was: TcpDiscoveryKubernetesIpFinder ThinClientKubernetesAddressFinder > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Affects Versions: 2.10 >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Docs changes related to the ticket > [IGNITE-13204|https://issues.apache.org/jira/browse/IGNITE-13204]. > The class > > TcpDiscoveryKubernetesIpFinder > ThinClientKubernetesAddressFinder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-13796: Description: Docs changes related to the ticket IGNITE-13204. The class https://issues.apache.org/jira/browse/IGNITE-13204 TcpDiscoveryKubernetesIpFinder ThinClientKubernetesAddressFinder was: Docs changes related to the ticket [IGNITE-13204|https://issues.apache.org/jira/browse/IGNITE-13204]. The class TcpDiscoveryKubernetesIpFinder ThinClientKubernetesAddressFinder > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Affects Versions: 2.10 >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Docs changes related to the ticket IGNITE-13204. > The class https://issues.apache.org/jira/browse/IGNITE-13204 > > TcpDiscoveryKubernetesIpFinder > ThinClientKubernetesAddressFinder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242825#comment-17242825 ] Denis A. Magda commented on IGNITE-13796: - [~timonin.maksim], from the pull request I see that we introduced the KubernetesConnectionConfiguration class as a member of the TcpDiscoveryKubernetesIpFinder. In the ticket description, you also mentioned the ThinClientKubernetesAddressFinder class. What the relation and dependency between all three? I'm going to ask professional technical writers to join the community and review your changes. Please do the following while they are onboarding: * Provide as many details as possible in the description of the ticket so that they understand what is the change about and how to explain it for developers. At least, my question above needs to be covered there. * Run your text through Grammarly. There are some missprints and typos that the tool will correct. > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Affects Versions: 2.10 >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > TcpDiscoveryKubernetesIpFinder > ThinClientKubernetesAddressFinder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242764#comment-17242764 ] Maksim Timonin commented on IGNITE-13796: - [~dmagda] [~dma...@apache.org] hi! Could you please review this documentation and example update? > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Affects Versions: 2.10 >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > TcpDiscoveryKubernetesIpFinder > ThinClientKubernetesAddressFinder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13353) DynamicCacheChangeBatch invokes partition validation for all caches
[
https://issues.apache.org/jira/browse/IGNITE-13353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242742#comment-17242742
]
Ignite TC Bot commented on IGNITE-13353:
{panel:title=Branch: [pull/8144/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8144/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}MVCC PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771119]]
* {color:#013220}IgnitePdsMvccTestSuite4:
NoUnnecessaryRebalancesTest.testNoRebalancesOnCacheCreation - PASSED{color}
{color:#8b}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771093]]
* {color:#013220}IgnitePdsTestSuite4:
NoUnnecessaryRebalancesTest.testNoRebalancesOnCacheCreation - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5771132buildTypeId=IgniteTests24Java8_RunAll]
> DynamicCacheChangeBatch invokes partition validation for all caches
> ---
>
> Key: IGNITE-13353
> URL: https://issues.apache.org/jira/browse/IGNITE-13353
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Sergey Uttsel
>Assignee: Sergey Uttsel
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now, DynamicCacheChangeBatch triggers partition validation for all
> caches. It can (and most possibly it will) show inconsistency between
> partitions in case of using DataStreamer. It will lead to the data rebalance,
> while it's not needed - updates should be streamed to backup nodes after some
> time due to asynchronous behavior of DataStramer
> In the attached log file cache was created at 1:33, it led to the partitions
> evictions right after that and to the rebalance at ~2:36(they have
> rebalanceDelay = 1hour). This behaviour led to these 2 drops almost to zero
> in write operations:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-10655) .NET client should have peerClassLoading property in IgniteConfiguration class
[ https://issues.apache.org/jira/browse/IGNITE-10655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexandr Shapkin reassigned IGNITE-10655: - Assignee: Alexandr Shapkin (was: Vladimir Pligin) > .NET client should have peerClassLoading property in IgniteConfiguration class > -- > > Key: IGNITE-10655 > URL: https://issues.apache.org/jira/browse/IGNITE-10655 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.7 >Reporter: Andrey Aleksandrov >Assignee: Alexandr Shapkin >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > In case if java server nodes in a cluster were set up with peerClassLoading > set to true then there is no way to start node via .NET client using > IgniteConfiguration (because the default value is false). > The only way to do it is using of the XML configuration. > Possibility to set this property from .Net client programmatically should be > added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13719) Thin client silently closes channel after inactivity
[
https://issues.apache.org/jira/browse/IGNITE-13719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-13719:
Release Note: Java thin: fix unexpected channel close due to inactivity
> Thin client silently closes channel after inactivity
>
>
> Key: IGNITE-13719
> URL: https://issues.apache.org/jira/browse/IGNITE-13719
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.9
>Reporter: jifwin
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.10, 2.9.1
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The following code works fine with ignite-core 2.8.0, but fails with 2.9.0
> (see the exception below). It looks like timeout is applied to client
> receiver thread. When it's not used for a while it gets closed silently.
> {code:java}
> public class IgniteDemo
> {
> public static final int TIMEOUT = 1000;
> public static void main(String[] args) throws InterruptedException
> {
> new IgniteDemo().run();
> }
> public void run() throws InterruptedException
> {
> final Ignite igniteServer = Ignition.start();
> final ClientConfiguration cfg = new
> ClientConfiguration().setAddresses("127.0.0.1:10800");
> cfg.setTimeout(TIMEOUT);
> final IgniteClient igniteClient = Ignition.startClient(cfg);
> final ClientCache cache =
> igniteClient.getOrCreateCache("test");
> Thread.sleep(TIMEOUT);
> cache.put(1, 1);
> Thread.sleep(TIMEOUT);
> cache.put(2, 2);
> }
> }
> {code}
> {code:java}
>
> Exception in thread "main"
> org.apache.ignite.client.ClientConnectionException: Channel is
> closedException in thread "main"
> org.apache.ignite.client.ClientConnectionException: Channel is closed at
> org.apache.ignite.internal.client.thin.TcpClientChannel.send(TcpClientChannel.java:236)
> at
> org.apache.ignite.internal.client.thin.TcpClientChannel.service(TcpClientChannel.java:217)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.service(ReliableChannel.java:198)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.affinityService(ReliableChannel.java:261)
> at
> org.apache.ignite.internal.client.thin.TcpClientCache.cacheSingleKeyOperation(TcpClientCache.java:508)
> at
> org.apache.ignite.internal.client.thin.TcpClientCache.put(TcpClientCache.java:127)
> at IgniteDemo.run(IgniteDemo.java:26) at IgniteDemo.main(IgniteDemo.java:13)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13633) thin clients cannot access the Ignite Service deployed through UriDeploymentSpi( java.lang.ClassNotFoundException)
[ https://issues.apache.org/jira/browse/IGNITE-13633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242669#comment-17242669 ] Vyacheslav Daradur commented on IGNITE-13633: - [~alex_pl], the changes lgtm. Let's getting new TC-bot visa just to be sure and I'll merge it. > thin clients cannot access the Ignite Service deployed through > UriDeploymentSpi( java.lang.ClassNotFoundException) > -- > > Key: IGNITE-13633 > URL: https://issues.apache.org/jira/browse/IGNITE-13633 > Project: Ignite > Issue Type: Bug > Components: managed services, thin client >Affects Versions: 2.9 >Reporter: xingzhou >Assignee: Aleksey Plekhanov >Priority: Critical > Fix For: 2.10 > > Attachments: ignite-deploy.zip > > Original Estimate: 24h > Time Spent: 3h > Remaining Estimate: 21h > > When the thin client is used to call the ignite service（ use ignite-urideploy > ）, the clientserviceinvokerequest will get the service classes, the local > classloader is used, and the classes cannot be found. Therefore, the > ignite-urideploy classloader should be added -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13806) Merge release notes for 2.9.1 into master
[ https://issues.apache.org/jira/browse/IGNITE-13806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242658#comment-17242658 ] Yaroslav Molochkov commented on IGNITE-13806: - [~mmuzaf], release notes for 291 > Merge release notes for 2.9.1 into master > - > > Key: IGNITE-13806 > URL: https://issues.apache.org/jira/browse/IGNITE-13806 > Project: Ignite > Issue Type: Task >Reporter: Yaroslav Molochkov >Assignee: Yaroslav Molochkov >Priority: Trivial > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13807) testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master
[ https://issues.apache.org/jira/browse/IGNITE-13807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13807: -- Fix Version/s: 2.10 > testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and > testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master > - > > Key: IGNITE-13807 > URL: https://issues.apache.org/jira/browse/IGNITE-13807 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Minor > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > Tests > EncryptedCacheNodeJoinTest.testClientNodeJoinInactiveClusterWithNewStaticCacheConfig > and > EncryptedCacheNodeJoinTest.testClientNodeJoinActiveClusterWithNewStaticCacheConfig > fails in master due to validation of the incorrect error message.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13807) testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master
[ https://issues.apache.org/jira/browse/IGNITE-13807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13807: -- Ignite Flags: (was: Docs Required,Release Notes Required) > testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and > testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master > - > > Key: IGNITE-13807 > URL: https://issues.apache.org/jira/browse/IGNITE-13807 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Tests > EncryptedCacheNodeJoinTest.testClientNodeJoinInactiveClusterWithNewStaticCacheConfig > and > EncryptedCacheNodeJoinTest.testClientNodeJoinActiveClusterWithNewStaticCacheConfig > fails in master due to validation of the incorrect error message.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13807) testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master
[ https://issues.apache.org/jira/browse/IGNITE-13807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13807: -- Description: Tests EncryptedCacheNodeJoinTest.testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and EncryptedCacheNodeJoinTest.testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master due to validation of the incorrect error message.. (was: Tests EncryptedCacheNodeJoinTest.testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and EncryptedCacheNodeJoinTest.testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master. ) > testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and > testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master > - > > Key: IGNITE-13807 > URL: https://issues.apache.org/jira/browse/IGNITE-13807 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Minor > > Tests > EncryptedCacheNodeJoinTest.testClientNodeJoinInactiveClusterWithNewStaticCacheConfig > and > EncryptedCacheNodeJoinTest.testClientNodeJoinActiveClusterWithNewStaticCacheConfig > fails in master due to validation of the incorrect error message.. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13807) testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master
Pavel Pereslegin created IGNITE-13807: - Summary: testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master Key: IGNITE-13807 URL: https://issues.apache.org/jira/browse/IGNITE-13807 Project: Ignite Issue Type: Bug Reporter: Pavel Pereslegin Assignee: Pavel Pereslegin Tests EncryptedCacheNodeJoinTest.testClientNodeJoinInactiveClusterWithNewStaticCacheConfig and EncryptedCacheNodeJoinTest.testClientNodeJoinActiveClusterWithNewStaticCacheConfig fails in master. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13806) Merge release notes for 2.9.1 into master
Yaroslav Molochkov created IGNITE-13806: --- Summary: Merge release notes for 2.9.1 into master Key: IGNITE-13806 URL: https://issues.apache.org/jira/browse/IGNITE-13806 Project: Ignite Issue Type: Task Reporter: Yaroslav Molochkov Assignee: Yaroslav Molochkov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13353) DynamicCacheChangeBatch invokes partition validation for all caches
[
https://issues.apache.org/jira/browse/IGNITE-13353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242635#comment-17242635
]
Ignite TC Bot commented on IGNITE-13353:
{panel:title=Branch: [pull/8144/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8144/head] Base: [master] : New Tests
(7)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5771044]]
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryNetworkIssuesTest.testNotSequentialFailTwoNodes - PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryNetworkIssuesTest.testSequentialFailTwoNodes - PASSED{color}
{color:#8b}Queries 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5771100]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlPartitionEvictionTest.testSqlConsistencyOnEviction[backups_count=0] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlPartitionEvictionTest.testSqlConsistencyOnEviction[backups_count=2] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlPartitionEvictionTest.testSqlConsistencyOnEviction[backups_count=1] -
PASSED{color}
{color:#8b}MVCC PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771119]]
* {color:#013220}IgnitePdsMvccTestSuite4:
NoUnnecessaryRebalancesTest.testNoRebalancesOnCacheCreation - PASSED{color}
{color:#8b}PDS 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771093]]
* {color:#013220}IgnitePdsTestSuite4:
NoUnnecessaryRebalancesTest.testNoRebalancesOnCacheCreation - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5771132buildTypeId=IgniteTests24Java8_RunAll]
> DynamicCacheChangeBatch invokes partition validation for all caches
> ---
>
> Key: IGNITE-13353
> URL: https://issues.apache.org/jira/browse/IGNITE-13353
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Reporter: Sergey Uttsel
>Assignee: Sergey Uttsel
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Right now, DynamicCacheChangeBatch triggers partition validation for all
> caches. It can (and most possibly it will) show inconsistency between
> partitions in case of using DataStreamer. It will lead to the data rebalance,
> while it's not needed - updates should be streamed to backup nodes after some
> time due to asynchronous behavior of DataStramer
> In the attached log file cache was created at 1:33, it led to the partitions
> evictions right after that and to the rebalance at ~2:36(they have
> rebalanceDelay = 1hour). This behaviour led to these 2 drops almost to zero
> in write operations:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-10075) .NET: Avoid binary configurations of Ignite Java service params and result when calling it from Ignite.NET
[
https://issues.apache.org/jira/browse/IGNITE-10075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242578#comment-17242578
]
Ignite TC Bot commented on IGNITE-10075:
{panel:title=Branch: [pull/8509/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8509/head] Base: [master] : New Tests
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Core Linux){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5770811]]
* {color:#013220}dll:
ServicesTypeAutoResolveTest.TestTypeAutoResolvingDynamicProxy - PASSED{color}
* {color:#013220}dll: ServicesTypeAutoResolveTest.TestCallJavaService -
PASSED{color}
{color:#8b}Platform .NET{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5770810]]
* {color:#013220}exe: ServicesTypeAutoResolveTest.TestCallJavaService -
PASSED{color}
* {color:#013220}exe:
ServicesTypeAutoResolveTest.TestTypeAutoResolvingDynamicProxy - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5770848buildTypeId=IgniteTests24Java8_RunAll]
> .NET: Avoid binary configurations of Ignite Java service params and result
> when calling it from Ignite.NET
> --
>
> Key: IGNITE-10075
> URL: https://issues.apache.org/jira/browse/IGNITE-10075
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.9
>Reporter: Alexey Kukushkin
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: .NET, sbcf
> Attachments: IGNITE-10075-from-2.9.0.patch, MyTest.cs
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Presently if there is an Ignite Java service taking parameters of complex
> (composite) types and returning a result of complex type then all the complex
> types must be explicitly specified in the binary configuration.
> We need to enhance Ignite not to require binary configuration assuming that
> we use the same type, package/namespace and field/property names on both the
> .NET and Java sides (or provide a custom name mapper for relaxed naming
> conventions).
> h2. Reproducer
> [https://github.com/kukushal/apache-ignite-issue10075.git]
> h3. ICalculator.java
> {code:java}
> package Apache.Ignite.Issue10075;
> public interface ICalculator {
> Result Calculate(Parameter p);
> }
> {code}
> h3. Parameter.java
> {code:java}
> package Apache.Ignite.Issue10075;
> public final class Parameter {
> private int id;
> private double val;
> public int getId() {
> return id;
> }
> public Parameter setId(int id) {
> this.id = id;
> return this;
> }
> public double getValue() {
> return val;
> }
> public Parameter setValue(double val) {
> this.val = val;
> return this;
> }
> }
> {code}
> h3. Result .java
> {code:java}
> package Apache.Ignite.Issue10075;
> public final class Result {
> private int id;
> private double value;
> public int getId() {
> return id;
> }
> public Result setId(int id) {
> this.id = id;
> return this;
> }
> public double getValue() {
> return value;
> }
> public Result setValue(double val) {
> this.value = val;
> return this;
> }
> }
> {code}
> h3. IgniteCalculatorService.java
> {code:java}
> package Apache.Ignite.Issue10075;
> import org.apache.ignite.services.Service;
> import org.apache.ignite.services.ServiceContext;
> public final class IgniteCalculatorService implements Service, ICalculator {
> @Override public Result Calculate(Parameter p) {
> return new Result().setId(p.getId()).setValue(p.getValue() *
> p.getValue());
> }
> @Override public void cancel(ServiceContext ctx) {
> }
> @Override public void init(ServiceContext ctx) {
> }
> @Override public void execute(ServiceContext ctx) {
> }
> }
> {code}
> h3. build.gradle
> {code:groovy}
> plugins {
> id 'java'
> }
> group 'apache.ignite.issue10075'
> version '1.0.0-SNAPSHOT'
> sourceCompatibility = 1.8
> repositories {
> mavenLocal()
> mavenCentral()
> }
> def igniteVer='2.9.0'
> dependencies {
> compile group: 'org.apache.ignite', name: 'ignite-core', version:
> igniteVer
> testCompile group: 'junit', name: 'junit', version: '4.12'
> }
> {code}
> h3. Apache.Ignite.Issue10075/ignite-config.xml
> {code:xml}
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
>
[jira] [Commented] (IGNITE-12824) Interoperable Ignite.NET Dates
[
https://issues.apache.org/jira/browse/IGNITE-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242515#comment-17242515
]
Pavel Tupitsyn commented on IGNITE-12824:
-
Linked to
[IEP-54|https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach]:
new type mappings are described there.
> Interoperable Ignite.NET Dates
> --
>
> Key: IGNITE-12824
> URL: https://issues.apache.org/jira/browse/IGNITE-12824
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.8
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
> Labels: .NET, iep-54, ignite-3, sbcf
> Fix For: 3.0
>
> Attachments: IGNITE-12824-from-2.9.0.patch
>
>
> *+The Problem+*
> Presently .NET API writes dates as composite Ignite objects. Only .NET
> clients can read such dates: any other client (JDBC, Java, etc) does not
> understand it without custom deserialization.
>
> It is still possible to configure .NET serialization to write dates as
> Ignite dates - see [DateTime Serialization
> note|https://ignite.apache.org/docs/latest/net-specific/net-platform-interoperability#types-compatibility].
> But then Ignite accepts only UTC dates, requiring the application developers
> to convert local dates to UTC dates and back. This task is not trivial:
> [DateTime.ToUniversalTime|https://docs.microsoft.com/en-us/dotnet/api/system.datetime.touniversaltime?view=netcore-3.1]
> uses calendars different from Java (and the .NET calendars are the invalid
> ones - especially for pre-1990 dates).
>
> The motivation for the current default behavior was probably the desire to
> keep the Time Zone information: Ignite dates do not store time zones.
>
> In our experience interoperability is more important than storing time zone
> info.
>
> *+The Solution+*
> # Always write .NET dates as portable Ignite dates: get rid of the
> {{BinaryReflectiveSerializer.ForceTimestamp}} flag that currently triggers
> this behavior.
> Keep the {{ForceTimestamp}} flag if saving .NET dates as transparent objects
> seems a useful case.
> # Automatically convert Local dates to UTC and back *inside* Ignite.NET.
> Add a {{BinaryReflectiveSerializer.UtcDate flag}} to disable this
> conversion. This prevents loosing the {{DateTime.Kind}} property of UTC
> dates. {{UtcDate}} set to true implies the existing behavior: Ignite gets
> UTC dates and throws a "Date must be in UTC" exception on an attempt to write
> a Local date. The {{UtcDate}} flag is false by default.
> # Use [NodaTime|https://nodatime.org/] for UTC<->Local conversions. Noda
> time uses Java calendars making the conversion truly portable.
>
> *+The Benefits+*
> # Portable dates is a more frequent use-case than storing time zone info for
> every date in Ignite. This becomes default behavior and the developers do not
> need to always explicitly configure it.
> # Non-trivial code to make the truly portable UTC<->Local conversion is
> implemented once inside Ignite instead of having every Ignite.NET application
> implementing it.
> +*References*+
> * [Dev-List
> Discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Interoperable-Ignite-NET-Dates-td49946.html]
> * IEP-TBD
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (IGNITE-13803) Scalar test failed due to incorrect Jackson dependency
[ https://issues.apache.org/jira/browse/IGNITE-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev resolved IGNITE-13803. -- Resolution: Fixed > Scalar test failed due to incorrect Jackson dependency > -- > > Key: IGNITE-13803 > URL: https://issues.apache.org/jira/browse/IGNITE-13803 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.10 >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > It's failed with > ``` > java.lang.ExceptionInInitializerError > Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible > Jackson version: 2.10.3``` > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaExamples?branch=%3Cdefault%3E=overview=builds# -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12824) Interoperable Ignite.NET Dates
[
https://issues.apache.org/jira/browse/IGNITE-12824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-12824:
Labels: .NET iep-54 ignite-3 sbcf (was: .NET ignite-3 sbcf)
> Interoperable Ignite.NET Dates
> --
>
> Key: IGNITE-12824
> URL: https://issues.apache.org/jira/browse/IGNITE-12824
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Affects Versions: 2.8
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
> Labels: .NET, iep-54, ignite-3, sbcf
> Fix For: 3.0
>
> Attachments: IGNITE-12824-from-2.9.0.patch
>
>
> *+The Problem+*
> Presently .NET API writes dates as composite Ignite objects. Only .NET
> clients can read such dates: any other client (JDBC, Java, etc) does not
> understand it without custom deserialization.
>
> It is still possible to configure .NET serialization to write dates as
> Ignite dates - see [DateTime Serialization
> note|https://ignite.apache.org/docs/latest/net-specific/net-platform-interoperability#types-compatibility].
> But then Ignite accepts only UTC dates, requiring the application developers
> to convert local dates to UTC dates and back. This task is not trivial:
> [DateTime.ToUniversalTime|https://docs.microsoft.com/en-us/dotnet/api/system.datetime.touniversaltime?view=netcore-3.1]
> uses calendars different from Java (and the .NET calendars are the invalid
> ones - especially for pre-1990 dates).
>
> The motivation for the current default behavior was probably the desire to
> keep the Time Zone information: Ignite dates do not store time zones.
>
> In our experience interoperability is more important than storing time zone
> info.
>
> *+The Solution+*
> # Always write .NET dates as portable Ignite dates: get rid of the
> {{BinaryReflectiveSerializer.ForceTimestamp}} flag that currently triggers
> this behavior.
> Keep the {{ForceTimestamp}} flag if saving .NET dates as transparent objects
> seems a useful case.
> # Automatically convert Local dates to UTC and back *inside* Ignite.NET.
> Add a {{BinaryReflectiveSerializer.UtcDate flag}} to disable this
> conversion. This prevents loosing the {{DateTime.Kind}} property of UTC
> dates. {{UtcDate}} set to true implies the existing behavior: Ignite gets
> UTC dates and throws a "Date must be in UTC" exception on an attempt to write
> a Local date. The {{UtcDate}} flag is false by default.
> # Use [NodaTime|https://nodatime.org/] for UTC<->Local conversions. Noda
> time uses Java calendars making the conversion truly portable.
>
> *+The Benefits+*
> # Portable dates is a more frequent use-case than storing time zone info for
> every date in Ignite. This becomes default behavior and the developers do not
> need to always explicitly configure it.
> # Non-trivial code to make the truly portable UTC<->Local conversion is
> implemented once inside Ignite instead of having every Ignite.NET application
> implementing it.
> +*References*+
> * [Dev-List
> Discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Interoperable-Ignite-NET-Dates-td49946.html]
> * IEP-TBD
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13803) Scalar test failed due to incorrect Jackson dependency
[ https://issues.apache.org/jira/browse/IGNITE-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242512#comment-17242512 ] Alexey Zinoviev commented on IGNITE-13803: -- After excluding dependency in "example" POM from ignite-ml RDD tests, scalar suite, ML project and all examples are executed without errors > Scalar test failed due to incorrect Jackson dependency > -- > > Key: IGNITE-13803 > URL: https://issues.apache.org/jira/browse/IGNITE-13803 > Project: Ignite > Issue Type: Bug > Components: ml >Affects Versions: 2.10 >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > It's failed with > ``` > java.lang.ExceptionInInitializerError > Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible > Jackson version: 2.10.3``` > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaExamples?branch=%3Cdefault%3E=overview=builds# -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13496) Java thin: Use non-blocking socket IO
[ https://issues.apache.org/jira/browse/IGNITE-13496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242499#comment-17242499 ] Pavel Tupitsyn commented on IGNITE-13496: - Merged to master: 338165afadd3b6979b4655ee2f03f3b9c2228236 > Java thin: Use non-blocking socket IO > -- > > Key: IGNITE-13496 > URL: https://issues.apache.org/jira/browse/IGNITE-13496 > Project: Ignite > Issue Type: Improvement > Components: thin client >Affects Versions: 2.9 >Reporter: Pavel Tupitsyn >Assignee: Pavel Tupitsyn >Priority: Major > Fix For: 2.10 > > Time Spent: 6h 20m > Remaining Estimate: 0h > > IGNITE-7623 introduces async APIs to the Java thin client. However, socket > writes still cause user thread blocking and thus reduce scalability. > Investigate and prepare an IEP to use non-blocking IO. > This ticket does not affect user-facing APIs, only changes the way we do IO > internally. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13805) Add support for cache group restore from a snapshot on the same topology (inactive cluster)
[ https://issues.apache.org/jira/browse/IGNITE-13805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Pereslegin updated IGNITE-13805: -- Labels: iep-43 (was: ) > Add support for cache group restore from a snapshot on the same topology > (inactive cluster) > --- > > Key: IGNITE-13805 > URL: https://issues.apache.org/jira/browse/IGNITE-13805 > Project: Ignite > Issue Type: New Feature >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-43 > > Add a CLI command (and public API?) to restore a cache group from a snapshot. > Limitations: > - inactive cluster > - partition distribution has not changed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13805) Add support for cache group restore from a snapshot on the same topology (inactive cluster)
Pavel Pereslegin created IGNITE-13805: - Summary: Add support for cache group restore from a snapshot on the same topology (inactive cluster) Key: IGNITE-13805 URL: https://issues.apache.org/jira/browse/IGNITE-13805 Project: Ignite Issue Type: New Feature Reporter: Pavel Pereslegin Assignee: Pavel Pereslegin Add a CLI command (and public API?) to restore a cache group from a snapshot. Limitations: - inactive cluster - partition distribution has not changed -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13804) Java thin: avoid buffer copies in synchronous operations
Pavel Tupitsyn created IGNITE-13804:
---
Summary: Java thin: avoid buffer copies in synchronous operations
Key: IGNITE-13804
URL: https://issues.apache.org/jira/browse/IGNITE-13804
Project: Ignite
Issue Type: Improvement
Components: thin client
Reporter: Pavel Tupitsyn
{{org.apache.ignite.internal.client.thin.TcpClientChannel#send}} creates a
buffer copy, because the buffer will be returned to the pool upon leaving the
scope, but we need it to survive longer while NIO framework processes it.
However, for synchronous requests we block the thread anyway, so an extra copy
can be avoided. See discussion in
[#8483|https://github.com/apache/ignite/pull/8483#discussion_r533915757]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13793) ODBC: Implement SQLRowCount for select queries
[ https://issues.apache.org/jira/browse/IGNITE-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242461#comment-17242461 ] Pavel Tupitsyn commented on IGNITE-13793: - [~isapego] LGTM > ODBC: Implement SQLRowCount for select queries > -- > > Key: IGNITE-13793 > URL: https://issues.apache.org/jira/browse/IGNITE-13793 > Project: Ignite > Issue Type: Improvement > Components: odbc >Affects Versions: 2.9 >Reporter: Igor Sapego >Assignee: Igor Sapego >Priority: Major > Fix For: 2.10 > > Time Spent: 10m > Remaining Estimate: 0h > > SQLRowCount() should return estimation of row count of the query. Currently, > we can not provide any estimations of this kind, but we still need to > implement this function as sometimes some third-party software uses it. It is > proposed to use some kind of constant value, e.g. page size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13803) Scalar test failed due to incorrect Jackson dependency
Alexey Zinoviev created IGNITE-13803: Summary: Scalar test failed due to incorrect Jackson dependency Key: IGNITE-13803 URL: https://issues.apache.org/jira/browse/IGNITE-13803 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.10 Reporter: Alexey Zinoviev Assignee: Alexey Zinoviev Fix For: 2.10 It's failed with ``` java.lang.ExceptionInInitializerError Caused by: com.fasterxml.jackson.databind.JsonMappingException: Incompatible Jackson version: 2.10.3``` https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ScalaExamples?branch=%3Cdefault%3E=overview=builds# -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13793) ODBC: Implement SQLRowCount for select queries
[
https://issues.apache.org/jira/browse/IGNITE-13793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242444#comment-17242444
]
Ignite TC Bot commented on IGNITE-13793:
{panel:title=Branch: [pull/8525/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8525/head] Base: [master] : New Tests
(1924)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform C++ (Win x64 / Debug){color} [[tests
949|https://ci.ignite.apache.org/viewLog.html?buildId=5770873]]
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestBasic -
PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryScan
- PASSED{color}
* {color:#013220}IgniteOdbcTest: ApiRobustnessTestSuite: TestSQLGetStmtAttr -
PASSED{color}
* {color:#013220}IgniteOdbcTest: ApplicationDataBufferTestSuite:
TestPutStringToLong - PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQuerySql
- PASSED{color}
* {color:#013220}IgniteOdbcTest: ApplicationDataBufferTestSuite:
TestPutStringToTiny - PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestInitialQueryText
- PASSED{color}
... and 938 new tests
{color:#8b}Platform C++ CMake (Win x64 / Debug){color} [[tests
971|https://ci.ignite.apache.org/viewLog.html?buildId=5770880]]
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionFloor - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlNumericFunctionTestSuite:
TestNumericFunctionLog - PASSED{color}
* {color:#013220}IgniteOdbcTest: SqlDateTimeFunctionTestSuite: TestCurrentDate
- PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForCacheNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForClientNodes -
PASSED{color}
* {color:#013220}IgniteCoreTest: CacheQueryTestSuite:
TestFieldsQueryByteArrayInsertSelect - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForDaemons -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForHost - PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForOldest -
PASSED{color}
* {color:#013220}IgniteCoreTest: ContinuousQueryTestSuite: TestBasic -
PASSED{color}
* {color:#013220}IgniteCoreTest: ClusterTestSuite: IgniteForRandom -
PASSED{color}
... and 960 new tests
{color:#8b}Platform C++ CMake (Linux){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5770879]]
* {color:#013220}IgniteOdbcTest: QueriesTestSuite: TestAffectedRowsOnSelect -
PASSED{color}
{color:#8b}Platform C++ (Win x64 / Release){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5770874]]
* {color:#013220}IgniteOdbcTest: QueriesTestSuite: TestAffectedRowsOnSelect -
PASSED{color}
{color:#8b}Platform C++ CMake (Linux Clang){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5770878]]
* {color:#013220}IgniteOdbcTest: QueriesTestSuite: TestAffectedRowsOnSelect -
PASSED{color}
{color:#8b}Platform C++ CMake (Win x64 / Release){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5770881]]
* {color:#013220}IgniteOdbcTest: QueriesTestSuite: TestAffectedRowsOnSelect -
PASSED{color}
{panel}
[TeamCity *- Run :: Thin Client*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5770886buildTypeId=IgniteTests24Java8_RunThinClient]
> ODBC: Implement SQLRowCount for select queries
> --
>
> Key: IGNITE-13793
> URL: https://issues.apache.org/jira/browse/IGNITE-13793
> Project: Ignite
> Issue Type: Improvement
> Components: odbc
>Affects Versions: 2.9
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> SQLRowCount() should return estimation of row count of the query. Currently,
> we can not provide any estimations of this kind, but we still need to
> implement this function as sometimes some third-party software uses it. It is
> proposed to use some kind of constant value, e.g. page size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11998) Fix DataPageScan for fragmented pages.
[ https://issues.apache.org/jira/browse/IGNITE-11998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242443#comment-17242443 ] Maxim Muzafarov commented on IGNITE-11998: -- [~ibessonov] Thank you! Yes, I'm currently working on it. > Fix DataPageScan for fragmented pages. > -- > > Key: IGNITE-11998 > URL: https://issues.apache.org/jira/browse/IGNITE-11998 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.10 > > > Fragmented pages crash JVM when accessed by DataPageScan scanner/query > optimized scanner. It happens when scanner accesses data in later chunk in > fragmented entry but treats it like the first one, expecting length of the > payload, which is absent and replaced with raw entry data. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13742) Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
[
https://issues.apache.org/jira/browse/IGNITE-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242397#comment-17242397
]
Ivan Bessonov commented on IGNITE-13742:
All those failures have nothing to do with my changes, I checked them. Waiting
for MVCC suite to rerun makes no sense, it fails with execution timeout must of
the times. .NET is even worse, it seems like we don't have enough agents. Scala
Examples fail in master.
> Fix failed
> WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
> -
>
> Key: IGNITE-13742
> URL: https://issues.apache.org/jira/browse/IGNITE-13742
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-47
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code is to blame:
>
> {code:java}
> // Reinitialized discovery manager won't have a valid consistentId on
> creation.
> discoMgr.consistentId(ctx.pdsFolderResolver().resolveFolders().consistentId());
> {code}
> More specifically: "***.consistentId" invocation with valid consistent id
> from ANY source.
>
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5803772702668480758=testDetails]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13742) Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
[
https://issues.apache.org/jira/browse/IGNITE-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242398#comment-17242398
]
Ivan Bessonov commented on IGNITE-13742:
[~sergeychugunov] can you merge it?
> Fix failed
> WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
> -
>
> Key: IGNITE-13742
> URL: https://issues.apache.org/jira/browse/IGNITE-13742
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-47
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code is to blame:
>
> {code:java}
> // Reinitialized discovery manager won't have a valid consistentId on
> creation.
> discoMgr.consistentId(ctx.pdsFolderResolver().resolveFolders().consistentId());
> {code}
> More specifically: "***.consistentId" invocation with valid consistent id
> from ANY source.
>
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5803772702668480758=testDetails]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13742) Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
[
https://issues.apache.org/jira/browse/IGNITE-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242396#comment-17242396
]
Ignite TC Bot commented on IGNITE-13742:
{panel:title=Branch: [pull/8524/head] Base: [master] : Possible Blockers
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}MVCC Cache 7{color} [[tests 2 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5770850]]
* IgniteCacheMvccTestSuite7:
GridCacheDhtPreloadWaitForBackupsWithPersistenceTest.testNodeForceShutdown -
Test has low fail rate in base branch 0,0% and is not flaky
* IgniteCacheMvccTestSuite7:
CachePartitionLossWithPersistenceTest.testConsistencyAfterResettingLostPartitions_2
- Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Platform .NET (Long Running){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5770634]]
* exe: CacheAbstractTest.TestCacheConfigurationExpiryPolicy - Test has low fail
rate in base branch 0,0% and is not flaky
{color:#d04437}Scala (Examples){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771376]]
* org.apache.ignite.scalar.testsuites.ScalarExamplesSelfTestSuite:
org.apache.ignite.scalar.testsuites.ScalarExamplesSelfTestSuite. - History for
base branch is absent.
{panel}
{panel:title=Branch: [pull/8524/head] Base: [master] : New Tests
(20)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#8b}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5770580]]
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryNetworkIssuesTest.testNotSequentialFailTwoNodes - PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryNetworkIssuesTest.testSequentialFailTwoNodes - PASSED{color}
{color:#8b}Examples{color} [[tests
14|https://ci.ignite.apache.org/viewLog.html?buildId=5770562]]
* {color:#013220}IgniteExamplesSelfTestSuite:
DecisionTreeClassificationExportImportExampleSelfTest.testExample -
PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
SVMExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
KMeansClusterizationExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
GaussianNaiveBayesExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
RandomForestClassificationExportImportExampleSelfTest.testExample -
PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
GDBOnTreesRegressionExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
GDBOnTreesClassificationExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
LinearRegressionExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
LogisticRegressionExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
RandomForestRegressionExportImportExampleSelfTest.testExample - PASSED{color}
* {color:#013220}IgniteExamplesSelfTestSuite:
DecisionTreeRegressionExportImportExampleSelfTest.testExample - PASSED{color}
... and 3 new tests
{color:#8b}Queries 1{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=5770636]]
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlPartitionEvictionTest.testSqlConsistencyOnEviction[backups_count=0] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlPartitionEvictionTest.testSqlConsistencyOnEviction[backups_count=2] -
PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite:
SqlPartitionEvictionTest.testSqlConsistencyOnEviction[backups_count=1] -
PASSED{color}
{color:#8b}Scala (Examples){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771376]]
*
{color:#8b}org.apache.ignite.scalar.testsuites.ScalarExamplesSelfTestSuite:
org.apache.ignite.scalar.testsuites.ScalarExamplesSelfTestSuite. - FAILED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5770668buildTypeId=IgniteTests24Java8_RunAll]
> Fix failed
> WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
> -
>
> Key: IGNITE-13742
> URL: https://issues.apache.org/jira/browse/IGNITE-13742
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-47
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code is to blame:
>
> {code:java}
> // Reinitialized discovery manager won't have a valid consistentId on
> creation.
>
[jira] [Commented] (IGNITE-13190) Core defragmentation functions
[
https://issues.apache.org/jira/browse/IGNITE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242390#comment-17242390
]
Ignite TC Bot commented on IGNITE-13190:
{panel:title=Branch: [pull/7984/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7984/head] Base: [master] : New Tests
(34)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5771011]]
* {color:#013220}IgniteBasicTestSuite: LinkMapTest.test - PASSED{color}
{color:#8b}PDS (Indexing){color} [[tests
12|https://ci.ignite.apache.org/viewLog.html?buildId=5770325]]
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testIndexingWithComplexKeyAndMVCC -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testIndexingWithIntegerKey - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverIncompletedPartition1 -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testIndexingWithComplexKey - PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverIncompletedIndex -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverIncompletedPartition2 -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testDefragmentedPartitionCreated -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverRestartWithoutDefragmentation
- PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testSuccessfulDefragmentation -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testIndexingWithIntegerKeyAndMVCC -
PASSED{color}
* {color:#013220}IgnitePdsWithIndexingTestSuite:
IgnitePdsIndexingDefragmentationTest.testFailoverOnLastStage - PASSED{color}
... and 1 new tests
{color:#8b}PDS 4{color} [[tests
21|https://ci.ignite.apache.org/viewLog.html?buildId=5770330]]
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationEncryptionTest.testFailoverIncompletedPartition2 -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationEncryptionTest.testFailoverIncompletedPartition1 -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationEncryptionTest.testFailoverRestartWithoutDefragmentation
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationEncryptionTest.testFailoverIncompletedIndex -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationEncryptionTest.testDefragmentedPartitionCreated -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationRandomLruEvictionTest.testFailoverIncompletedIndex -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationRandomLruEvictionTest.testSuccessfulDefragmentation -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationRandomLruEvictionTest.testFailoverIncompletedPartition2
- PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationTest.testFailoverOnLastStage - PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationEncryptionTest.testSuccessfulDefragmentation -
PASSED{color}
* {color:#013220}IgnitePdsTestSuite4:
IgnitePdsDefragmentationRandomLruEvictionTest.testDefragmentedPartitionCreated
- PASSED{color}
... and 10 new tests
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5770369buildTypeId=IgniteTests24Java8_RunAll]
> Core defragmentation functions
> --
>
> Key: IGNITE-13190
> URL: https://issues.apache.org/jira/browse/IGNITE-13190
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Sergey Chugunov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-47
> Time Spent: 20h 40m
> Remaining Estimate: 0h
>
> The following set of functions covering defragmentation happy-case needed:
> * Initialization of defragmentation manager when node is started in
> maintenance mode.
> * Information about partition files is gathered by defrag mgr.
> * For each partition file corresponding file of defragmented partition is
> created and initialized.
> * Keys are transferred from old partitions to new partitions.
> * Checkpointer is aware of new partition files and flushes defragmented
> memory to new partition files.
>
> No fault-tolerance code nor index defragmentation mappings are
[jira] [Created] (IGNITE-13802) GridCacheOffheapManager#addPartitions ignores candidate pages count for index partition
Ivan Bessonov created IGNITE-13802: -- Summary: GridCacheOffheapManager#addPartitions ignores candidate pages count for index partition Key: IGNITE-13802 URL: https://issues.apache.org/jira/browse/IGNITE-13802 Project: Ignite Issue Type: Bug Reporter: Ivan Bessonov Assignee: Ivan Bessonov It also marks page as dirty despite doing nothing with it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13801) ODBC: Check ODBC driver with Ab Initio and fix all issues
Igor Sapego created IGNITE-13801: Summary: ODBC: Check ODBC driver with Ab Initio and fix all issues Key: IGNITE-13801 URL: https://issues.apache.org/jira/browse/IGNITE-13801 Project: Ignite Issue Type: Improvement Components: odbc Affects Versions: 2.9 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 2.10 I want to check our ODBC driver with Ab Initio and fix issues if there are any. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13520) Сlient node with a static encrypted cache configuration can generate an encryption key when joining.
[ https://issues.apache.org/jira/browse/IGNITE-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242364#comment-17242364 ] Pavel Pereslegin commented on IGNITE-13520: --- [~nizhikov], thanks for the review. > Сlient node with a static encrypted cache configuration can generate an > encryption key when joining. > > > Key: IGNITE-13520 > URL: https://issues.apache.org/jira/browse/IGNITE-13520 > Project: Ignite > Issue Type: Bug >Affects Versions: 2.9 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: encryption > Fix For: 2.10 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Currently, when a client node joins a cluster with a static encrypted cache > configuration, it generates an encryption key for that cache and sends it to > the cluster (just like the server node does). > _SpringEncryptedCacheRestartClientTest_ reproduces this behavior and it is > unexpected, it happens due to IGNITE-13567 (see > _GridEncryptionManager#collectJoiningNodeData_). > The client node should not generate encryption keys and should be able to > start without configuring EncryptionSPI. > After doing some research on possible solutions, we decided to reject node > joining in such a situation, because there is no clean and simple way to > distribute the same encryption key between server nodes that are already in > the cluster (we have to either add discovery overhead, block the exchange, or > add an additional exchange to be able to distribute keys between server nodes > that are already in the cluster). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13800) Provide distributed metastorage interface
Alexey Goncharuk created IGNITE-13800: - Summary: Provide distributed metastorage interface Key: IGNITE-13800 URL: https://issues.apache.org/jira/browse/IGNITE-13800 Project: Ignite Issue Type: New Feature Reporter: Alexey Goncharuk We need to crystallize the metastorage interface prototype from the IEP to understand how it will be integrated with other system components. Need to cover: * Asynchrony aspects * Possible error codes (connection failure -> unknown result vs Raft failure -> known result, etc) * Complex multi-updates (aka transactions) * Watchers. Each node can watch all updates and filter locally or adjust the watched ranges dynamically (consistency is important here) These interfaces are considered "client" interfaces as they will be available on all nodes in the cluster -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13800) Provide distributed metastorage interface
[ https://issues.apache.org/jira/browse/IGNITE-13800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-13800: -- Labels: iep-61 ignite-3 (was: ) > Provide distributed metastorage interface > - > > Key: IGNITE-13800 > URL: https://issues.apache.org/jira/browse/IGNITE-13800 > Project: Ignite > Issue Type: New Feature >Reporter: Alexey Goncharuk >Priority: Major > Labels: iep-61, ignite-3 > > We need to crystallize the metastorage interface prototype from the IEP to > understand how it will be integrated with other system components. > Need to cover: > * Asynchrony aspects > * Possible error codes (connection failure -> unknown result vs Raft failure > -> known result, etc) > * Complex multi-updates (aka transactions) > * Watchers. Each node can watch all updates and filter locally or adjust the > watched ranges dynamically (consistency is important here) > These interfaces are considered "client" interfaces as they will be available > on all nodes in the cluster -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13799) Provide a required storage interface for metastorage and partitions for replication protocol
[ https://issues.apache.org/jira/browse/IGNITE-13799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-13799: -- Labels: iep-61 ignite-3 (was: ) > Provide a required storage interface for metastorage and partitions for > replication protocol > > > Key: IGNITE-13799 > URL: https://issues.apache.org/jira/browse/IGNITE-13799 > Project: Ignite > Issue Type: New Feature >Reporter: Alexey Goncharuk >Priority: Major > Labels: iep-61, ignite-3 > > We need to identify two storage interfaces that will be interacting with the > replication protocol: > * Distributed metastorage persistent state machine > * Partition persistent state machine > The interfaces for the said storages most likely will be quite different, but > still will have some common ground. Need to define them so that we can start > moving the page memory infrastructure to Ignite-3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13799) Provide a required storage interface for metastorage and partitions for replication protocol
Alexey Goncharuk created IGNITE-13799: - Summary: Provide a required storage interface for metastorage and partitions for replication protocol Key: IGNITE-13799 URL: https://issues.apache.org/jira/browse/IGNITE-13799 Project: Ignite Issue Type: New Feature Reporter: Alexey Goncharuk We need to identify two storage interfaces that will be interacting with the replication protocol: * Distributed metastorage persistent state machine * Partition persistent state machine The interfaces for the said storages most likely will be quite different, but still will have some common ground. Need to define them so that we can start moving the page memory infrastructure to Ignite-3 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13798) Prototype Raft implementation port to a separate zero-dependency Ignite module
Alexey Goncharuk created IGNITE-13798: - Summary: Prototype Raft implementation port to a separate zero-dependency Ignite module Key: IGNITE-13798 URL: https://issues.apache.org/jira/browse/IGNITE-13798 Project: Ignite Issue Type: New Feature Reporter: Alexey Goncharuk Assignee: Alexey Goncharuk We need to check whether it is reasonable and feasible to port the etcd Raft implementation [1] to Java, maintaining the same API interaction model: * Raft instance is a single-threaded state machine with methods to accept messages, return progress to be processed by a raft client, and tick callback * Raft instance does not actively send messages, not does it actively write to persistent log or the state machine The implementation should demonstrate how the module will be used with omitted components: Raft Log, State Machine, Messaging, Timer. The implementation must cover: * Ability to provide leader/follower callbacks * Ability to read linearizable and relaxed commit indexes The implementation may cover: * Replication group reconfiguration The implementation prototype does not cover: * Multi-raft groups * Asynchronous state machine mutation -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13797) Calcite bug. CREATE TABLE with WHERE SELECT 1;
Stanilovsky Evgeny created IGNITE-13797:
---
Summary: Calcite bug. CREATE TABLE with WHERE SELECT 1;
Key: IGNITE-13797
URL: https://issues.apache.org/jira/browse/IGNITE-13797
Project: Ignite
Issue Type: Improvement
Components: sql
Reporter: Stanilovsky Evgeny
CREATE TABLE TABLE_E061_09_01_04 ( A INT PRIMARY KEY, CC INTEGER ); SELECT A
FROM TABLE_E061_09_01_04 WHERE A = ( SELECT 1 );
fires:
{noformat}
java.lang.AssertionError: RelSubset
[rel#4121:RelSubset#7.IGNITE.[].single.rewindable.uncorrelated] has wrong best
cost 1021.13999. Correct cost is 1057.0
at org.apache.calcite.util.Litmus$1.fail(Litmus.java:31)
at
org.apache.calcite.plan.volcano.VolcanoPlanner.isValid(VolcanoPlanner.java:647)
at
org.apache.calcite.plan.volcano.VolcanoPlanner.ensureRegistered(VolcanoPlanner.java:610)
at
org.apache.calcite.plan.volcano.VolcanoRuleCall.transformTo(VolcanoRuleCall.java:148)
at
org.apache.calcite.plan.RelOptRuleCall.transformTo(RelOptRuleCall.java:268)
at
org.apache.calcite.plan.RelOptRuleCall.transformTo(RelOptRuleCall.java:283)
at
org.apache.calcite.rel.convert.ConverterRule.onMatch(ConverterRule.java:169)
at
org.apache.calcite.plan.volcano.VolcanoRuleCall.onMatch(VolcanoRuleCall.java:229)
at
org.apache.calcite.plan.volcano.TopDownRuleDriver.applyGenerator(TopDownRuleDriver.java:142)
at
org.apache.calcite.plan.volcano.TopDownRuleDriver.access$600(TopDownRuleDriver.java:47)
at
org.apache.calcite.plan.volcano.TopDownRuleDriver$ApplyRule.perform(TopDownRuleDriver.java:519)
at
org.apache.calcite.plan.volcano.TopDownRuleDriver.drive(TopDownRuleDriver.java:101)
at
org.apache.calcite.plan.volcano.VolcanoPlanner.findBestExp(VolcanoPlanner.java:510)
at
org.apache.calcite.tools.Programs$RuleSetProgram.run(Programs.java:312)
at
org.apache.ignite.internal.processors.query.calcite.prepare.IgnitePlanner.transform(IgnitePlanner.java:258)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.optimize(ExecutionServiceImpl.java:616)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:568)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareSingle(ExecutionServiceImpl.java:542)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.prepareQuery(ExecutionServiceImpl.java:501)
at
org.apache.ignite.internal.processors.query.calcite.prepare.QueryPlanCacheImpl.queryPlan(QueryPlanCacheImpl.java:84)
at
org.apache.ignite.internal.processors.query.calcite.exec.ExecutionServiceImpl.executeQuery(ExecutionServiceImpl.java:378)
at
org.apache.ignite.internal.processors.query.calcite.CalciteQueryProcessor.query(CalciteQueryProcessor.java:240)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2787)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2743)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-13796: Affects Version/s: 2.10 > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Affects Versions: 2.10 >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > TcpDiscoveryKubernetesIpFinder > ThinClientKubernetesAddressFinder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13796) Update docs for the kubernetes module)
Maksim Timonin created IGNITE-13796: --- Summary: Update docs for the kubernetes module) Key: IGNITE-13796 URL: https://issues.apache.org/jira/browse/IGNITE-13796 Project: Ignite Issue Type: New Feature Reporter: Maksim Timonin -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-13796: Summary: Update docs for the kubernetes module (was: Update docs for the kubernetes module)) > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin reassigned IGNITE-13796: --- Assignee: Maksim Timonin > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13796) Update docs for the kubernetes module
[ https://issues.apache.org/jira/browse/IGNITE-13796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maksim Timonin updated IGNITE-13796: Description: TcpDiscoveryKubernetesIpFinder ThinClientKubernetesAddressFinder > Update docs for the kubernetes module > - > > Key: IGNITE-13796 > URL: https://issues.apache.org/jira/browse/IGNITE-13796 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Maksim Timonin >Priority: Major > > TcpDiscoveryKubernetesIpFinder > ThinClientKubernetesAddressFinder -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13794) Add partition awareness to NodeJS client
[ https://issues.apache.org/jira/browse/IGNITE-13794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Semyon Danilov updated IGNITE-13794: Description: Implement [IEP-23|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] for Node.js thin client. > Add partition awareness to NodeJS client > > > Key: IGNITE-13794 > URL: https://issues.apache.org/jira/browse/IGNITE-13794 > Project: Ignite > Issue Type: Task >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > > Implement > [IEP-23|https://cwiki.apache.org/confluence/display/IGNITE/IEP-23%3A+Best+Effort+Affinity+for+thin+clients] > for Node.js thin client. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13795) java.nio.file.InvalidPathException: Illegal char <:> at lock page on windows
[
https://issues.apache.org/jira/browse/IGNITE-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Bessonov updated IGNITE-13795:
---
Ignite Flags: (was: Docs Required,Release Notes Required)
> java.nio.file.InvalidPathException: Illegal char <:> at lock page on windows
>
>
> Key: IGNITE-13795
> URL: https://issues.apache.org/jira/browse/IGNITE-13795
> Project: Ignite
> Issue Type: Bug
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
>
> {code:java}
> Exception in thread "Thread-1" java.nio.file.InvalidPathException: Illegal
> char <:> at index 109:
> C:\BuildAgent\work\d501ae8146bd8253\i2test\var\suite-thin_clients\art-gg-ult\work\diagnostic\page_lock_dump_0:0:0:0:0:0:0:1,127.0.0.1,172.23.240.1,172.25.2.217:47500_2020_06_22_17_24_06_377
> at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
> at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
> at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
> at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
> at java.io.File.toPath(File.java:2234)
> at
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.dumpprocessors.ToFileDumpProcessor.saveToFile(ToFileDumpProcessor.java:69)
> at
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.dumpprocessors.ToFileDumpProcessor.toFileDump(ToFileDumpProcessor.java:53)
> at
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.PageLockTrackerManager.onHangThreads(PageLockTrackerManager.java:123)
> at
> org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.SharedPageLockTracker$TimeOutWorker.run(SharedPageLockTracker.java:385)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13795) java.nio.file.InvalidPathException: Illegal char <:> at lock page on windows
Ivan Bessonov created IGNITE-13795:
--
Summary: java.nio.file.InvalidPathException: Illegal char <:> at
lock page on windows
Key: IGNITE-13795
URL: https://issues.apache.org/jira/browse/IGNITE-13795
Project: Ignite
Issue Type: Bug
Reporter: Ivan Bessonov
Assignee: Ivan Bessonov
{code:java}
Exception in thread "Thread-1" java.nio.file.InvalidPathException: Illegal char
<:> at index 109:
C:\BuildAgent\work\d501ae8146bd8253\i2test\var\suite-thin_clients\art-gg-ult\work\diagnostic\page_lock_dump_0:0:0:0:0:0:0:1,127.0.0.1,172.23.240.1,172.25.2.217:47500_2020_06_22_17_24_06_377
at sun.nio.fs.WindowsPathParser.normalize(WindowsPathParser.java:182)
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:153)
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
at java.io.File.toPath(File.java:2234)
at
org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.dumpprocessors.ToFileDumpProcessor.saveToFile(ToFileDumpProcessor.java:69)
at
org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.dumpprocessors.ToFileDumpProcessor.toFileDump(ToFileDumpProcessor.java:53)
at
org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.PageLockTrackerManager.onHangThreads(PageLockTrackerManager.java:123)
at
org.apache.ignite.internal.processors.cache.persistence.diagnostic.pagelocktracker.SharedPageLockTracker$TimeOutWorker.run(SharedPageLockTracker.java:385)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13794) Add partition awareness to NodeJS client
Semyon Danilov created IGNITE-13794: --- Summary: Add partition awareness to NodeJS client Key: IGNITE-13794 URL: https://issues.apache.org/jira/browse/IGNITE-13794 Project: Ignite Issue Type: Task Reporter: Semyon Danilov Assignee: Semyon Danilov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12337) [ML] Redesign the package structure
[ https://issues.apache.org/jira/browse/IGNITE-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev resolved IGNITE-12337. -- Resolution: Won't Fix > [ML] Redesign the package structure > --- > > Key: IGNITE-12337 > URL: https://issues.apache.org/jira/browse/IGNITE-12337 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Minor > Fix For: 2.10 > > > The problem is the next: a lot of classes and algorithms are located in not > the appropriate places and are not grouped in the high-level packages -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12337) [ML] Redesign the package structure
[ https://issues.apache.org/jira/browse/IGNITE-12337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12337: - Fix Version/s: (was: 2.10) > [ML] Redesign the package structure > --- > > Key: IGNITE-12337 > URL: https://issues.apache.org/jira/browse/IGNITE-12337 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Minor > > The problem is the next: a lot of classes and algorithms are located in not > the appropriate places and are not grouped in the high-level packages -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-12288) [ML] Replace assert logic with exceptions
[ https://issues.apache.org/jira/browse/IGNITE-12288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12288: - Fix Version/s: (was: 2.10) > [ML] Replace assert logic with exceptions > - > > Key: IGNITE-12288 > URL: https://issues.apache.org/jira/browse/IGNITE-12288 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Minor > > 1) Add exceptions instead of assert logic > 2) Add tests for the proposed exceptions -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13793) ODBC: Implement SQLRowCount for select queries
Igor Sapego created IGNITE-13793: Summary: ODBC: Implement SQLRowCount for select queries Key: IGNITE-13793 URL: https://issues.apache.org/jira/browse/IGNITE-13793 Project: Ignite Issue Type: Improvement Components: odbc Affects Versions: 2.9 Reporter: Igor Sapego Assignee: Igor Sapego Fix For: 2.10 SQLRowCount() should return estimation of row count of the query. Currently, we can not provide any estimations of this kind, but we still need to implement this function as sometimes some third-party software uses it. It is proposed to use some kind of constant value, e.g. page size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-11998) Fix DataPageScan for fragmented pages.
[ https://issues.apache.org/jira/browse/IGNITE-11998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242332#comment-17242332 ] Ivan Bessonov commented on IGNITE-11998: Hi [~mmuzaf], just found out that this issue is on you now. DataPageScan optimization was disabled as a part of https://issues.apache.org/jira/browse/IGNITE-11982. It comes with a bunch of other fixes, which sucks. But you can still use it as a reference, many of those changes must be reapplied back. BTW, what's your plan? How are you going to fix it? > Fix DataPageScan for fragmented pages. > -- > > Key: IGNITE-11998 > URL: https://issues.apache.org/jira/browse/IGNITE-11998 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Maxim Muzafarov >Priority: Critical > Fix For: 2.10 > > > Fragmented pages crash JVM when accessed by DataPageScan scanner/query > optimized scanner. It happens when scanner accesses data in later chunk in > fragmented entry but treats it like the first one, expecting length of the > payload, which is absent and replaced with raw entry data. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13640) Opencensus module has no runtime dependencies.
[ https://issues.apache.org/jira/browse/IGNITE-13640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242303#comment-17242303 ] Vyacheslav Koptilin commented on IGNITE-13640: -- Hello [~alapin], LGTM. Merged to the master branch. > Opencensus module has no runtime dependencies. > -- > > Key: IGNITE-13640 > URL: https://issues.apache.org/jira/browse/IGNITE-13640 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Assignee: Alexander Lapin >Priority: Major > Labels: 2.9.1-rc > Fix For: 2.10 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > Need to add dependencies to pom.xml > * io.opencensus.opencensus-impl-core - 0.22.0 version > * io.grpc.grpc-context - 1.19.0 version > * com.lmax.disruptor - 3.4.2 version > * com.google.guava.guava - 26.0-android version -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13770) Ignite.dataRegionMetrics throws NPE with empty persisted region
[
https://issues.apache.org/jira/browse/IGNITE-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-13770:
-
Ignite Flags: (was: Release Notes Required)
> Ignite.dataRegionMetrics throws NPE with empty persisted region
> ---
>
> Key: IGNITE-13770
> URL: https://issues.apache.org/jira/browse/IGNITE-13770
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.9
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Labels: easyfix
> Fix For: 2.10, 2.9.1
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.checkpointBufferPagesCount(PageMemoryImpl.java:1823)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataRegionMetricsImpl.getUsedCheckpointBufferPages(DataRegionMetricsImpl.java:287)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataRegionMetricsSnapshot.(DataRegionMetricsSnapshot.java:108)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.memoryMetrics(IgniteCacheDatabaseSharedManager.java:815)
> at
> org.apache.ignite.internal.IgniteKernal.dataRegionMetrics(IgniteKernal.java:3773)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12079) [ML][Umbrella] Add advanced preprocessing techniques
[ https://issues.apache.org/jira/browse/IGNITE-12079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-12079: - Fix Version/s: (was: 2.10) > [ML][Umbrella] Add advanced preprocessing techniques > > > Key: IGNITE-12079 > URL: https://issues.apache.org/jira/browse/IGNITE-12079 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > > *Main goal:* > To reduce the gap between Apache Spark and Apache Ignite in preprocessing > operations. The reducing of the gap could help with loading Spark ML > Pipelines to Ignite ML. > > Next steps: > # Add Frequency Encoder > # Add two Imputing Strategies (MIN, MAX, COUNT, MOST_FREQUENT, > LEAST_FREQUENT) > # Add RobustScaler (will be added in Spark 3.0) > # Add CountVectorizer > # Add FeatureHasher > # Add QuantileDiscretizer > # Add Locality Sensitive Hashing (LSH) > # Add LabelEncoder > # Add RevertStringIndexing > # Add multi-column preprocessor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10426) [ML] Spread parameter isKeepRawLabels across all models
[ https://issues.apache.org/jira/browse/IGNITE-10426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-10426: - Fix Version/s: (was: 2.10) > [ML] Spread parameter isKeepRawLabels across all models > --- > > Key: IGNITE-10426 > URL: https://issues.apache.org/jira/browse/IGNITE-10426 > Project: Ignite > Issue Type: Improvement > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > > Currently, a few models has the parameter isKeepRawLabels and threshold to > change predicted value to one of class labels 1 or 0. > Discuss this in dev-list and think how to solve this task to optimize > MultiClassModel > Possible solution: > * add these methods to common model > * add this method to MultiClassModel and use reflection to check this > parameter in apply method for example -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-10870) [ML] Add an example for KNN/LogReg and multi-class task full Iris dataset
[ https://issues.apache.org/jira/browse/IGNITE-10870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-10870: - Fix Version/s: (was: 2.10) > [ML] Add an example for KNN/LogReg and multi-class task full Iris dataset > - > > Key: IGNITE-10870 > URL: https://issues.apache.org/jira/browse/IGNITE-10870 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Minor > Labels: newbie > > Add a one or two examples for KNN/LogReg and Iris dataset with 3 classes -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13672) [ML] Add initial JSON export/import support for all models
[ https://issues.apache.org/jira/browse/IGNITE-13672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-13672: - Labels: important (was: ) > [ML] Add initial JSON export/import support for all models > -- > > Key: IGNITE-13672 > URL: https://issues.apache.org/jira/browse/IGNITE-13672 > Project: Ignite > Issue Type: Sub-task > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Labels: important > Fix For: 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > This approaches uses JAXB project abilities to import in and export from > human-readable JSON format. > Should include: > * Basic interfaces > * Implementations for all models > * Examples for all models (maybe export only) > * Tests with import/export to the temp directory -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-6642) [Umbrella] Model export/import to PMML and custom JSON format
[ https://issues.apache.org/jira/browse/IGNITE-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-6642: Fix Version/s: (was: 2.10) > [Umbrella] Model export/import to PMML and custom JSON format > - > > Key: IGNITE-6642 > URL: https://issues.apache.org/jira/browse/IGNITE-6642 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > > > We need to be able to export/import Ignite model versions across clusters > with different versions and have exchangable & human-readable format for > inference with different systems like scikit-learn, Spark ML and etc > The PMML format is a good choice here: > PMML - Predictive Model Markup Language is XML based language which used in > SPARK MLlib and others platforms. > Here some additional info about PMML: > (i) [http://dmg.org/pmml/v4-3/GeneralStructure.html] > (i) [https://github.com/jpmml/jpmml-model] > > But PMML has limitation support for Ensembles like Random Forest, Gradient > Boosted Trees, Stacking, Bagging and so on. > These cases could be covered with our own JSON format which could be easily > parsed in another system. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-6642) [Umbrella] Model export/import to PMML and custom JSON format
[ https://issues.apache.org/jira/browse/IGNITE-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Zinoviev updated IGNITE-6642: Labels: (was: important) > [Umbrella] Model export/import to PMML and custom JSON format > - > > Key: IGNITE-6642 > URL: https://issues.apache.org/jira/browse/IGNITE-6642 > Project: Ignite > Issue Type: New Feature > Components: ml >Reporter: Alexey Zinoviev >Assignee: Alexey Zinoviev >Priority: Major > Fix For: 2.10 > > > > We need to be able to export/import Ignite model versions across clusters > with different versions and have exchangable & human-readable format for > inference with different systems like scikit-learn, Spark ML and etc > The PMML format is a good choice here: > PMML - Predictive Model Markup Language is XML based language which used in > SPARK MLlib and others platforms. > Here some additional info about PMML: > (i) [http://dmg.org/pmml/v4-3/GeneralStructure.html] > (i) [https://github.com/jpmml/jpmml-model] > > But PMML has limitation support for Ensembles like Random Forest, Gradient > Boosted Trees, Stacking, Bagging and so on. > These cases could be covered with our own JSON format which could be easily > parsed in another system. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13770) Ignite.dataRegionMetrics throws NPE with empty persisted region
[
https://issues.apache.org/jira/browse/IGNITE-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242288#comment-17242288
]
Stanislav Lukyanov commented on IGNITE-13770:
-
LGTM
> Ignite.dataRegionMetrics throws NPE with empty persisted region
> ---
>
> Key: IGNITE-13770
> URL: https://issues.apache.org/jira/browse/IGNITE-13770
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.9
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
> Labels: easyfix
> Fix For: 2.10
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {code}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.checkpointBufferPagesCount(PageMemoryImpl.java:1823)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataRegionMetricsImpl.getUsedCheckpointBufferPages(DataRegionMetricsImpl.java:287)
> at
> org.apache.ignite.internal.processors.cache.persistence.DataRegionMetricsSnapshot.(DataRegionMetricsSnapshot.java:108)
> at
> org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager.memoryMetrics(IgniteCacheDatabaseSharedManager.java:815)
> at
> org.apache.ignite.internal.IgniteKernal.dataRegionMetrics(IgniteKernal.java:3773)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-11346) Remote client authentication failed for the CommandHandler in the case where it optional on the server
[ https://issues.apache.org/jira/browse/IGNITE-11346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242268#comment-17242268 ] Ivan Bessonov commented on IGNITE-11346: [~Maxoid] I know it's been a long time, but what's the status of this issue? It was ready to merge, like, 18 months ago. > Remote client authentication failed for the CommandHandler in the case where > it optional on the server > -- > > Key: IGNITE-11346 > URL: https://issues.apache.org/jira/browse/IGNITE-11346 > Project: Ignite > Issue Type: Bug > Components: clients, security, thin client >Affects Versions: 2.7 >Reporter: Maxim Karavaev >Assignee: Maxim Karavaev >Priority: Minor > Time Spent: 1.5h > Remaining Estimate: 0h > > h2. Preposition: > Custom _GridSecurityProcessor_ implementation allows optional authentication. > With other words, if some credentials are presents then authentication > performed, otherwise - not (some restricted SecurityContext returned). > REST API works fine. If credentials are present or the auth request was made > then the auth works as desired, if not - it also works but only for some > authorized requests. > h2. The problem: > _CommandHandler_ which is used for controlling a cluster through the CLI > script _command.sh|bat_ doesn't respect credential parameters and sends auth > request only in case of authentication exception for a regular request. In > the described case of optional authentication it never happens, so the result > always depends on the "default" Permissions. > h2. Possible solution: > Change _GridClientNioTcpConnection_ to always send first an auth request in > case of provided credentials. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13388) apache-ignite deb package depends on a non-existent package and can't be installed on Debian 10
[
https://issues.apache.org/jira/browse/IGNITE-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242262#comment-17242262
]
Ilya Kasnacheev commented on IGNITE-13388:
--
Fix pushed to master.
> apache-ignite deb package depends on a non-existent package and can't be
> installed on Debian 10
> ---
>
> Key: IGNITE-13388
> URL: https://issues.apache.org/jira/browse/IGNITE-13388
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Artem Budnikov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: 2.9.1-rc
> Fix For: 2.10, 2.9.1
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The apache-ignite deb package v. 2.8.1 depends on 'openjdk-8-jdk', which is
> only available in Debian stretch and isn't available in later Debian
> distributions. An attempt to install the package gives this error:
> {code:java}
> $ sudo apt-get install apache-ignite=2.8.1-1
> ...
> The following packages have unmet dependencies:
> apache-ignite : Depends: openjdk-8-jdk but it is not installable or
> oracle-java8-installer but it is not installable
> E: Unable to correct problems, you have held broken packages{code}
> Package information:
> {code:java}
> $ apt-cache show apache-ignite=2.8.1-1
> Package: apache-ignite
> Version: 2.8.1-1
> Architecture: all
> Maintainer: Petr Ivanov
> Installed-Size: 572071
> Depends: openjdk-8-jdk | oracle-java8-installer, systemd, passwd
> Section: misc
> Priority: optional
> Homepage: https://ignite.apache.org
> Description: Apache Ignite In-Memory Computing, Database and Caching Platform
> Ignite™ is a memory-centric distributed database, caching, and processing
> platform for transactional, analytical, and streaming workloads, delivering
> in-memory speeds at petabyte scale
> Description-md5: 6a59db03fa1e142387abef6ef6bb0d83
> Filename: pool/main/a/apache-ignite_2.8.1-1_all.deb
> SHA1: 67d197a5e582f6ea7c66da26a755f937f8e16fc9
> SHA256: fc9a274ecb82716905d4120a715e9c74441dfed67831874eb3c35c4953bfc90d
> Size: 399746094
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13742) Fix failed WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
[
https://issues.apache.org/jira/browse/IGNITE-13742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242261#comment-17242261
]
Sergey Chugunov commented on IGNITE-13742:
--
[~ibessonov],
Patch looks good to me, lets wait for TC results and see if there are any
broken tests.
> Fix failed
> WalModeChangeAdvancedSelfTest.testMaintenanceIsSkippedIfWasFixedManuallyOnDowntime
> -
>
> Key: IGNITE-13742
> URL: https://issues.apache.org/jira/browse/IGNITE-13742
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Labels: IEP-47
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This code is to blame:
>
> {code:java}
> // Reinitialized discovery manager won't have a valid consistentId on
> creation.
> discoMgr.consistentId(ctx.pdsFolderResolver().resolveFolders().consistentId());
> {code}
> More specifically: "***.consistentId" invocation with valid consistent id
> from ANY source.
>
>
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5803772702668480758=testDetails]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-13388) apache-ignite deb package depends on a non-existent package and can't be installed on Debian 10
[
https://issues.apache.org/jira/browse/IGNITE-13388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilya Kasnacheev updated IGNITE-13388:
-
Fix Version/s: 2.9.1
> apache-ignite deb package depends on a non-existent package and can't be
> installed on Debian 10
> ---
>
> Key: IGNITE-13388
> URL: https://issues.apache.org/jira/browse/IGNITE-13388
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.8.1
>Reporter: Artem Budnikov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: 2.9.1-rc
> Fix For: 2.10, 2.9.1
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The apache-ignite deb package v. 2.8.1 depends on 'openjdk-8-jdk', which is
> only available in Debian stretch and isn't available in later Debian
> distributions. An attempt to install the package gives this error:
> {code:java}
> $ sudo apt-get install apache-ignite=2.8.1-1
> ...
> The following packages have unmet dependencies:
> apache-ignite : Depends: openjdk-8-jdk but it is not installable or
> oracle-java8-installer but it is not installable
> E: Unable to correct problems, you have held broken packages{code}
> Package information:
> {code:java}
> $ apt-cache show apache-ignite=2.8.1-1
> Package: apache-ignite
> Version: 2.8.1-1
> Architecture: all
> Maintainer: Petr Ivanov
> Installed-Size: 572071
> Depends: openjdk-8-jdk | oracle-java8-installer, systemd, passwd
> Section: misc
> Priority: optional
> Homepage: https://ignite.apache.org
> Description: Apache Ignite In-Memory Computing, Database and Caching Platform
> Ignite™ is a memory-centric distributed database, caching, and processing
> platform for transactional, analytical, and streaming workloads, delivering
> in-memory speeds at petabyte scale
> Description-md5: 6a59db03fa1e142387abef6ef6bb0d83
> Filename: pool/main/a/apache-ignite_2.8.1-1_all.deb
> SHA1: 67d197a5e582f6ea7c66da26a755f937f8e16fc9
> SHA256: fc9a274ecb82716905d4120a715e9c74441dfed67831874eb3c35c4953bfc90d
> Size: 399746094
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12885) Checkpoint thread executes partitions fsync in single thread
[ https://issues.apache.org/jira/browse/IGNITE-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242259#comment-17242259 ] Ilya Kasnacheev commented on IGNITE-12885: -- I don't remember rejecting it, but if you say so... > Checkpoint thread executes partitions fsync in single thread > > > Key: IGNITE-12885 > URL: https://issues.apache.org/jira/browse/IGNITE-12885 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > It should use "asyncRunner" if it was configured, this will optimize > checkpoint speed. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13775) U.ReentrantReadWriteLockTracer improper realization.
[ https://issues.apache.org/jira/browse/IGNITE-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242223#comment-17242223 ] Stanilovsky Evgeny commented on IGNITE-13775: - !screenshot-1.png! > U.ReentrantReadWriteLockTracer improper realization. > > > Key: IGNITE-13775 > URL: https://issues.apache.org/jira/browse/IGNITE-13775 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.9 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Attachments: image-2020-12-01-13-51-39-048.png, screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > ReentrantReadWriteLockTracer accepts ReentrantReadWriteLock as a delegate and > stores delegates for readLock and writeLock. But > ReentrantReadWriteLock#isWriteLockedByCurrentThread uses sync object to > evaluate the result instead of writeLock, and ReentrantReadWriteLockTracer > has it's own sync object. > As a result, if ReentrantReadWriteLockTracer is used to create checkpoint > lock (when IGNITE_PDS_LOG_CP_READ_LOCK_HOLDERS=true), > GridCacheDatabaseSharedManager#checkpointLockIsHeldByThread doesn't work > correctly: it returns false when checkpoint lock is acquired. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13775) U.ReentrantReadWriteLockTracer improper realization.
[ https://issues.apache.org/jira/browse/IGNITE-13775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stanilovsky Evgeny updated IGNITE-13775: Attachment: screenshot-1.png > U.ReentrantReadWriteLockTracer improper realization. > > > Key: IGNITE-13775 > URL: https://issues.apache.org/jira/browse/IGNITE-13775 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.9 >Reporter: Stanilovsky Evgeny >Assignee: Stanilovsky Evgeny >Priority: Major > Attachments: image-2020-12-01-13-51-39-048.png, screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > ReentrantReadWriteLockTracer accepts ReentrantReadWriteLock as a delegate and > stores delegates for readLock and writeLock. But > ReentrantReadWriteLock#isWriteLockedByCurrentThread uses sync object to > evaluate the result instead of writeLock, and ReentrantReadWriteLockTracer > has it's own sync object. > As a result, if ReentrantReadWriteLockTracer is used to create checkpoint > lock (when IGNITE_PDS_LOG_CP_READ_LOCK_HOLDERS=true), > GridCacheDatabaseSharedManager#checkpointLockIsHeldByThread doesn't work > correctly: it returns false when checkpoint lock is acquired. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13702) Fix description of soLinger for DiscoveryTcpSpi.
[ https://issues.apache.org/jira/browse/IGNITE-13702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13702: -- Description: Fix description of soLinger for DiscoveryTcpSpi. (was: Fix description of soLibger for DiscoveryTcpSpi.) > Fix description of soLinger for DiscoveryTcpSpi. > > > Key: IGNITE-13702 > URL: https://issues.apache.org/jira/browse/IGNITE-13702 > Project: Ignite > Issue Type: Improvement > Components: documentation >Affects Versions: 2.10 >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Minor > Fix For: 2.9, 2.10 > > Time Spent: 20m > Remaining Estimate: 0h > > Fix description of soLinger for DiscoveryTcpSpi. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13705) Another node fails with failure of target node.
[ https://issues.apache.org/jira/browse/IGNITE-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Steshin updated IGNITE-13705: -- Fix Version/s: (was: 2.10) 2.9.1 > Another node fails with failure of target node. > --- > > Key: IGNITE-13705 > URL: https://issues.apache.org/jira/browse/IGNITE-13705 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: iep-45 > Fix For: 2.9.1 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The discovery ducktape test [1] has detected unexpected failure of another > node. > Scenario: > The nodes have relative places in the ring: N and N+1. Node N detects failure > of node N+1. Node N tries to connect to node N+2. Node N+2 checks backward > connection to node N+1. > Problem: > Node N can fail too. > Cause: > The timeout on node N to recover connection to node N+2 appears shorter than > timeout on node N+2 to check connection to N+1. > Fix: > Introduced a fundamental timeout value to check/recover connection based on > current configuration. The mentioned timeouts have been turned relative. The > timeout of backward connection check is now generally shorter than the > timeout to recover connection. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13705) Another node fails with failure of target node.
[ https://issues.apache.org/jira/browse/IGNITE-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-13705: -- Labels: iep-45 (was: ) > Another node fails with failure of target node. > --- > > Key: IGNITE-13705 > URL: https://issues.apache.org/jira/browse/IGNITE-13705 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: iep-45 > Fix For: 2.10 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The discovery ducktape test [1] has detected unexpected failure of another > node. > Scenario: > The nodes have relative places in the ring: N and N+1. Node N detects failure > of node N+1. Node N tries to connect to node N+2. Node N+2 checks backward > connection to node N+1. > Problem: > Node N can fail too. > Cause: > The timeout on node N to recover connection to node N+2 appears shorter than > timeout on node N+2 to check connection to N+1. > Fix: > Introduced a fundamental timeout value to check/recover connection based on > current configuration. The mentioned timeouts have been turned relative. The > timeout of backward connection check is now generally shorter than the > timeout to recover connection. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13705) Another node fails with failure of target node.
[ https://issues.apache.org/jira/browse/IGNITE-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242192#comment-17242192 ] Anton Vinogradov commented on IGNITE-13705: --- Merged to master. Thanks for your contribution. > Another node fails with failure of target node. > --- > > Key: IGNITE-13705 > URL: https://issues.apache.org/jira/browse/IGNITE-13705 > Project: Ignite > Issue Type: Bug >Reporter: Vladimir Steshin >Assignee: Vladimir Steshin >Priority: Major > Labels: iep-45 > Fix For: 2.10 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > The discovery ducktape test [1] has detected unexpected failure of another > node. > Scenario: > The nodes have relative places in the ring: N and N+1. Node N detects failure > of node N+1. Node N tries to connect to node N+2. Node N+2 checks backward > connection to node N+1. > Problem: > Node N can fail too. > Cause: > The timeout on node N to recover connection to node N+2 appears shorter than > timeout on node N+2 to check connection to N+1. > Fix: > Introduced a fundamental timeout value to check/recover connection based on > current configuration. The mentioned timeouts have been turned relative. The > timeout of backward connection check is now generally shorter than the > timeout to recover connection. > [1] > https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups
[ https://issues.apache.org/jira/browse/IGNITE-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Daschinskiy updated IGNITE-13572: -- Fix Version/s: 2.9.1 > Duplicates in select query during partition eviction for caches with 0 backups > -- > > Key: IGNITE-13572 > URL: https://issues.apache.org/jira/browse/IGNITE-13572 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.9, 2.8.1 >Reporter: Ivan Daschinskiy >Assignee: Konstantin Sirotkin >Priority: Major > Fix For: 2.10, 2.9.1 > > Attachments: SqlPartitionEvictionTest.java > > Time Spent: 4h 50m > Remaining Estimate: 0h > > Scenario: > # Start 2 nodes with indexed atomic partitioned cache with 0 backups. > # Load sufficient amout of data (or emulate slow removal from idx) > # Start another node. > # Perform SELECT * FROM . > Query result contains duplicates, result size is significantly bigger than > expected cache size. > Reproducer is attached. > Reproduced on 2.8.1, ongoing 2.9 and master -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13705) Another node fails with failure of target node.
[
https://issues.apache.org/jira/browse/IGNITE-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242177#comment-17242177
]
Ignite TC Bot commented on IGNITE-13705:
{panel:title=Branch: [pull/8484/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8484/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}SPI{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5768007]]
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryNetworkIssuesTest.testNotSequentialFailTwoNodes - PASSED{color}
* {color:#013220}IgniteSpiTestSuite:
TcpDiscoveryNetworkIssuesTest.testSequentialFailTwoNodes - PASSED{color}
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5768095buildTypeId=IgniteTests24Java8_RunAll]
> Another node fails with failure of target node.
> ---
>
> Key: IGNITE-13705
> URL: https://issues.apache.org/jira/browse/IGNITE-13705
> Project: Ignite
> Issue Type: Bug
>Reporter: Vladimir Steshin
>Assignee: Vladimir Steshin
>Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The discovery ducktape test [1] has detected unexpected failure of another
> node.
> Scenario:
> The nodes have relative places in the ring: N and N+1. Node N detects failure
> of node N+1. Node N tries to connect to node N+2. Node N+2 checks backward
> connection to node N+1.
> Problem:
> Node N can fail too.
> Cause:
> The timeout on node N to recover connection to node N+2 appears shorter than
> timeout on node N+2 to check connection to N+1.
> Fix:
> Introduced a fundamental timeout value to check/recover connection based on
> current configuration. The mentioned timeouts have been turned relative. The
> timeout of backward connection check is now generally shorter than the
> timeout to recover connection.
> [1]
> https://github.com/apache/ignite/blob/ignite-ducktape/modules/ducktests/tests/ignitetest/tests/discovery_test.py
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13680) Broken formatting rule for vm.swappiness.
[
https://issues.apache.org/jira/browse/IGNITE-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242175#comment-17242175
]
Ilya Kasnacheev commented on IGNITE-13680:
--
I have left a comment about getting rid of isRedHat check.
> Broken formatting rule for vm.swappiness.
> -
>
> Key: IGNITE-13680
> URL: https://issues.apache.org/jira/browse/IGNITE-13680
> Project: Ignite
> Issue Type: Improvement
> Components: general
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Shubin Nikolay
>Priority: Major
> Labels: newbie
> Attachments: OsConfigurationSuggestions.java
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignite start suggestions use float formatting for int value :
> {noformat}
> ^-- Reduce pages swapping ratio (set vm.swappiness=10.00 or less)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-13190) Core defragmentation functions
[ https://issues.apache.org/jira/browse/IGNITE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17242136#comment-17242136 ] Ivan Bessonov commented on IGNITE-13190: [~mmuzaf] thank you, I'll take a look at performance profiling tool. And, of course, we won't merge anything without TC results. > Core defragmentation functions > -- > > Key: IGNITE-13190 > URL: https://issues.apache.org/jira/browse/IGNITE-13190 > Project: Ignite > Issue Type: Sub-task >Reporter: Sergey Chugunov >Assignee: Ivan Bessonov >Priority: Major > Labels: IEP-47 > Time Spent: 20h 40m > Remaining Estimate: 0h > > The following set of functions covering defragmentation happy-case needed: > * Initialization of defragmentation manager when node is started in > maintenance mode. > * Information about partition files is gathered by defrag mgr. > * For each partition file corresponding file of defragmented partition is > created and initialized. > * Keys are transferred from old partitions to new partitions. > * Checkpointer is aware of new partition files and flushes defragmented > memory to new partition files. > > No fault-tolerance code nor index defragmentation mappings are needed in this > task. -- This message was sent by Atlassian Jira (v8.3.4#803005)
