[jira] [Commented] (IGNITE-11918) extend test coverage for KILL QUERY
[ https://issues.apache.org/jira/browse/IGNITE-11918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864173#comment-16864173 ] Pavel Kuznetsov commented on IGNITE-11918: -- updated, rerun: https://ci.ignite.apache.org/viewQueued.html?itemId=4118730 > extend test coverage for KILL QUERY > --- > > Key: IGNITE-11918 > URL: https://issues.apache.org/jira/browse/IGNITE-11918 > Project: Ignite > Issue Type: Test >Reporter: Pavel Kuznetsov >Assignee: Pavel Kuznetsov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently we have implemented KILL QUERY COMMAND. However not all cases > covered by tests and probably it doesn't work properly for all cases. > On first look need to add following test scenarios for KILL QUERY command: > 1) not stable topology - when node couldn't reserve partitions. > 2) map and reduce parts > 3) with concrete partition > 4) when partition pruning is work. > 5) local query > 6) distributed joins. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11908) OOM in MVCC PDS4
[ https://issues.apache.org/jira/browse/IGNITE-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-11908: --- Assignee: Ivan Pavlukhin > OOM in MVCC PDS4 > - > > Key: IGNITE-11908 > URL: https://issues.apache.org/jira/browse/IGNITE-11908 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Almost every time [MVCC PDS > 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds4&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv] > fails with OOM. Regular [PDS > 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds4&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=%3Cdefault%3E] > fails as well. Sometimes timeout occurs instead of OOM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11927) [IEP-35] Add ability to disable subset of metrics
Nikolay Izhikov created IGNITE-11927: Summary: [IEP-35] Add ability to disable subset of metrics Key: IGNITE-11927 URL: https://issues.apache.org/jira/browse/IGNITE-11927 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov Ignite should be able to enable or disable an arbitrary subset of the metrics. User should be able to do it in runtime. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11927) [IEP-35] Add ability to disable subset of metrics
[ https://issues.apache.org/jira/browse/IGNITE-11927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11927: - Labels: IEP-35 (was: ) > [IEP-35] Add ability to disable subset of metrics > - > > Key: IGNITE-11927 > URL: https://issues.apache.org/jira/browse/IGNITE-11927 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > > Ignite should be able to enable or disable an arbitrary subset of the metrics. > User should be able to do it in runtime. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11926) [IEP-35] Migrage GridJobMetricsProcessor
[ https://issues.apache.org/jira/browse/IGNITE-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11926: - Labels: IEP-35 (was: ) > [IEP-35] Migrage GridJobMetricsProcessor > > > Key: IGNITE-11926 > URL: https://issues.apache.org/jira/browse/IGNITE-11926 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > > After merging of IGNITE-11848 we should migrate `GridJobMetricsProcessor` to > the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11926) [IEP-35] Migrage GridJobMetricsProcessor
Nikolay Izhikov created IGNITE-11926: Summary: [IEP-35] Migrage GridJobMetricsProcessor Key: IGNITE-11926 URL: https://issues.apache.org/jira/browse/IGNITE-11926 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov After merging of IGNITE-11848 we should migrate `GridJobMetricsProcessor` to the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11925) [IEP-35] Migrage QueryMetrics
[ https://issues.apache.org/jira/browse/IGNITE-11925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11925: - Labels: IEP-35 (was: ) > [IEP-35] Migrage QueryMetrics > - > > Key: IGNITE-11925 > URL: https://issues.apache.org/jira/browse/IGNITE-11925 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > > After merging of IGNITE-11848 we should migrate `QueryMetrics` to the new > metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11925) [IEP-35] Migrage QueryMetrics
Nikolay Izhikov created IGNITE-11925: Summary: [IEP-35] Migrage QueryMetrics Key: IGNITE-11925 URL: https://issues.apache.org/jira/browse/IGNITE-11925 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov After merging of IGNITE-11848 we should migrate `QueryMetrics` to the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11924) [IEP-35] Migrate TransactionMetricsMxBean
Nikolay Izhikov created IGNITE-11924: Summary: [IEP-35] Migrate TransactionMetricsMxBean Key: IGNITE-11924 URL: https://issues.apache.org/jira/browse/IGNITE-11924 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov After merging of IGNITE-11848 we should migrate `TransactionMetricsMxBean` to the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11923) [IEP-35] Migrate IgniteMXBean
Nikolay Izhikov created IGNITE-11923: Summary: [IEP-35] Migrate IgniteMXBean Key: IGNITE-11923 URL: https://issues.apache.org/jira/browse/IGNITE-11923 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov After merging of IGNITE-11848 we should migrate `IgniteMXBean` to the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11922) [IEP-35] Migrate ClusterMetricsMxBean
Nikolay Izhikov created IGNITE-11922: Summary: [IEP-35] Migrate ClusterMetricsMxBean Key: IGNITE-11922 URL: https://issues.apache.org/jira/browse/IGNITE-11922 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov After merging of IGNITE-11848 we should migrate `ClusterMetricsMxBean` to the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11921) [IEP-35] Migrage CacheGroupMetrics
Nikolay Izhikov created IGNITE-11921: Summary: [IEP-35] Migrage CacheGroupMetrics Key: IGNITE-11921 URL: https://issues.apache.org/jira/browse/IGNITE-11921 Project: Ignite Issue Type: Improvement Reporter: Nikolay Izhikov After merging of IGNITE-11848 we should migrate `CacheGroupMetricsMXBean` to the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11921) [IEP-35] Migrate CacheGroupMetrics
[ https://issues.apache.org/jira/browse/IGNITE-11921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov updated IGNITE-11921: - Summary: [IEP-35] Migrate CacheGroupMetrics (was: [IEP-35] Migrage CacheGroupMetrics) > [IEP-35] Migrate CacheGroupMetrics > -- > > Key: IGNITE-11921 > URL: https://issues.apache.org/jira/browse/IGNITE-11921 > Project: Ignite > Issue Type: Improvement >Reporter: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > > After merging of IGNITE-11848 we should migrate `CacheGroupMetricsMXBean` to > the new metric framework. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11920) [IEP-35] Improve Metric API
Nikolay Izhikov created IGNITE-11920:
Summary: [IEP-35] Improve Metric API
Key: IGNITE-11920
URL: https://issues.apache.org/jira/browse/IGNITE-11920
Project: Ignite
Issue Type: Improvement
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
MetricRegistry may be made safer if we explicitly extract a group of metrics
for some Ignite entity(cache, service, etc.).
Internally, the registry will stay the same.
API proposition is:
{code:java}
MetricRegistry {
MetricSet default();
MetricSet group(String name);
}
MetricSet {
LongCounter counter();
void registrer(Metric m);
//other methods.
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11920) [IEP-35] Improve Metric API
[
https://issues.apache.org/jira/browse/IGNITE-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikolay Izhikov updated IGNITE-11920:
-
Labels: IEP-35 (was: )
> [IEP-35] Improve Metric API
> ---
>
> Key: IGNITE-11920
> URL: https://issues.apache.org/jira/browse/IGNITE-11920
> Project: Ignite
> Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
> Labels: IEP-35
>
> MetricRegistry may be made safer if we explicitly extract a group of metrics
> for some Ignite entity(cache, service, etc.).
> Internally, the registry will stay the same.
> API proposition is:
> {code:java}
> MetricRegistry {
> MetricSet default();
> MetricSet group(String name);
> }
> MetricSet {
> LongCounter counter();
> void registrer(Metric m);
> //other methods.
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11848) [IEP-35] Monitoring&Profiling. Phase 1
[ https://issues.apache.org/jira/browse/IGNITE-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864018#comment-16864018 ] Nikolay Izhikov commented on IGNITE-11848: -- [~agura] [~alex_pl] [~ascherbakov] [~daradurvs] [~Jokser] Guys, Thanks for the review! Phase 1 merged to master. > [IEP-35] Monitoring&Profiling. Phase 1 > -- > > Key: IGNITE-11848 > URL: https://issues.apache.org/jira/browse/IGNITE-11848 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 7h > Remaining Estimate: 0h > > Umbrella ticket for the IEP-35. Monitoring and profiling. > Phase 1 should include: > * NextGen monitoring subsystem implementation to manage > ** metrics > ** -lists- (will be implemented in the following tickets) > ** exporters > * JMX, SQLView, Log exporters > * Migration of existing metrics to new manager > * -Lists for all Ignite user API- -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11584) Implement batch insertion of new cache entries in FreeList to improve rebalancing
[ https://issues.apache.org/jira/browse/IGNITE-11584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864013#comment-16864013 ] Pavel Pereslegin commented on IGNITE-11584: --- "Platform .NET" suites hangs on master branch too (on test "Apache.Ignite.Core.Tests.Services.ServicesTest.TestCallJavaService"), not relates to changes in PR. > Implement batch insertion of new cache entries in FreeList to improve > rebalancing > - > > Key: IGNITE-11584 > URL: https://issues.apache.org/jira/browse/IGNITE-11584 > Project: Ignite > Issue Type: Sub-task >Affects Versions: 2.7 >Reporter: Pavel Pereslegin >Assignee: Pavel Pereslegin >Priority: Major > Labels: iep-32 > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Main goals: > * Implement batch insert operation into FreeList - insert several data rows > at once > * Use batch insertion in the preloader > > Implementation notes: > # Preloader cannot lock multiple cache entries at once, because this may > lead to a deadlock with concurrent batch updates. Therefore, it pre-creates > batch of data rows in the page memory, and then sequentially initializes the > cache entries one by one. > # Batch writing of data rows into data pages uses the free list as usual > because other approaches increase memory fragmentation (for example, using > only "reuse" or "most free" buckets). > # Eviction tracker assumes that only data pages with "heads" of fragmented > data row are tracked, so all other fragments of large data row should be > written on separate data pages (without other data rows which may cause page > tracking). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11848) [IEP-35] Monitoring&Profiling. Phase 1
[ https://issues.apache.org/jira/browse/IGNITE-11848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16864011#comment-16864011 ] Aleksey Plekhanov commented on IGNITE-11848: [~NIzhikov] I've looked at your PR. Patch looks good to me. > [IEP-35] Monitoring&Profiling. Phase 1 > -- > > Key: IGNITE-11848 > URL: https://issues.apache.org/jira/browse/IGNITE-11848 > Project: Ignite > Issue Type: Task >Affects Versions: 2.7 >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Labels: IEP-35 > Fix For: 2.8 > > Time Spent: 6h 50m > Remaining Estimate: 0h > > Umbrella ticket for the IEP-35. Monitoring and profiling. > Phase 1 should include: > * NextGen monitoring subsystem implementation to manage > ** metrics > ** -lists- (will be implemented in the following tickets) > ** exporters > * JMX, SQLView, Log exporters > * Migration of existing metrics to new manager > * -Lists for all Ignite user API- -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11584) Implement batch insertion of new cache entries in FreeList to improve rebalancing
[
https://issues.apache.org/jira/browse/IGNITE-11584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863965#comment-16863965
]
Ignite TC Bot commented on IGNITE-11584:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 2 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=4116331]]
{color:#d04437}Platform .NET{color} [[tests 0 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=4116333]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4113416&buildTypeId=IgniteTests24Java8_RunAll]
> Implement batch insertion of new cache entries in FreeList to improve
> rebalancing
> -
>
> Key: IGNITE-11584
> URL: https://issues.apache.org/jira/browse/IGNITE-11584
> Project: Ignite
> Issue Type: Sub-task
>Affects Versions: 2.7
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Labels: iep-32
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Main goals:
> * Implement batch insert operation into FreeList - insert several data rows
> at once
> * Use batch insertion in the preloader
>
> Implementation notes:
> # Preloader cannot lock multiple cache entries at once, because this may
> lead to a deadlock with concurrent batch updates. Therefore, it pre-creates
> batch of data rows in the page memory, and then sequentially initializes the
> cache entries one by one.
> # Batch writing of data rows into data pages uses the free list as usual
> because other approaches increase memory fragmentation (for example, using
> only "reuse" or "most free" buckets).
> # Eviction tracker assumes that only data pages with "heads" of fragmented
> data row are tracked, so all other fragments of large data row should be
> written on separate data pages (without other data rows which may cause page
> tracking).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11771) Kubernetes discovery support for non-ready pods
[ https://issues.apache.org/jira/browse/IGNITE-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863956#comment-16863956 ] Roman Shtykh commented on IGNITE-11771: --- [~Mmuzaf] Thank you for pointing at it! Sorry I should have checked it on TC as well. Will fix. > Kubernetes discovery support for non-ready pods > --- > > Key: IGNITE-11771 > URL: https://issues.apache.org/jira/browse/IGNITE-11771 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.7 >Reporter: Balazs Peterfi >Assignee: Denis Magda >Priority: Minor > Time Spent: 40m > Remaining Estimate: 0h > > I have a use case where Ignite is running in embedded mode and on start-up > there is a time consuming task to warm-up the cache. During that time > Kubernetes sees the pods as not ready due to the loading, thus the current > implementation doesn't return them as potential members. Eventually they > would become ready and see each-other but by then it would be a split-brain > situation. > The idea is to return IPs not only for "ready" pods but for "not ready" ones > as well in case the discovery client is configured that way. See more details > here: > [https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#endpointsubset-v1-core] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10973) Migrate example module tests from Junit 4 to 5
[ https://issues.apache.org/jira/browse/IGNITE-10973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863955#comment-16863955 ] Ivan Fedotov commented on IGNITE-10973: --- [~Pavlukhin], Hi! In general I managed with migration examples module to JUnit 5. What I did: * added JUnit5 dependencies to parent/pom.xml. JUnit4 still works without any changes: junit-vintage allows us to use the previous version. * added junit47 provider to use the JUnit version in the project >= 4.7 * changed suite runner: from Suite.class to JUnitPlatform.class * in examples module changed annotations and uncommented ignored tests However, TC bot shows as blocker those tests which for some reasons do not have history on master branch [1]. I checked logs and tests have failures because of functionality. Moreover, they fail on master branch locally for the same reasons. But TC history for them is empty and they are not marked as ignored in code. Can be reason in TC/TC bot infrastucture, what do you think? [1] [https://mtcga.gridgain.com/pr.html?serverId=apache&suiteId=IgniteTests24Java8_RunAll&branchForTc=pull/6606/head&action=Latest] > Migrate example module tests from Junit 4 to 5 > -- > > Key: IGNITE-10973 > URL: https://issues.apache.org/jira/browse/IGNITE-10973 > Project: Ignite > Issue Type: Sub-task >Reporter: Ivan Fedotov >Assignee: Ivan Fedotov >Priority: Major > Labels: iep-30 > Time Spent: 0.5h > Remaining Estimate: 0h > > For more information refer parent task. > Migrate from Junit 4 to 5 in the example module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11771) Kubernetes discovery support for non-ready pods
[
https://issues.apache.org/jira/browse/IGNITE-11771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863950#comment-16863950
]
Maxim Muzafarov commented on IGNITE-11771:
--
[~shroman], Folks,
it seems that Check Style Suite [1] began to fail with the exception below due
to the current commit.
Could you please check?
{code:java}
[Step 2/2] [ERROR]
/opt/buildagent/work/69588afcb2ab3382/modules/kubernetes/src/main/java/org/apache/ignite/spi/discovery/tcp/ipfinder/kubernetes/TcpDiscoveryKubernetesIpFinder.java:323:
'VARIABLE_DEF' should be separated from previous statement.
[EmptyLineSeparator]{code}
[1]
[https://ci.ignite.apache.org/viewLog.html?buildId=4117329&buildTypeId=IgniteTests24Java8_CheckCodeStyle]
> Kubernetes discovery support for non-ready pods
> ---
>
> Key: IGNITE-11771
> URL: https://issues.apache.org/jira/browse/IGNITE-11771
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Balazs Peterfi
>Assignee: Denis Magda
>Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I have a use case where Ignite is running in embedded mode and on start-up
> there is a time consuming task to warm-up the cache. During that time
> Kubernetes sees the pods as not ready due to the loading, thus the current
> implementation doesn't return them as potential members. Eventually they
> would become ready and see each-other but by then it would be a split-brain
> situation.
> The idea is to return IPs not only for "ready" pods but for "not ready" ones
> as well in case the discovery client is configured that way. See more details
> here:
> [https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.13/#endpointsubset-v1-core]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11908) OOM in MVCC PDS4
[ https://issues.apache.org/jira/browse/IGNITE-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin updated IGNITE-11908: Description: Almost every time [MVCC PDS 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds4&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv] fails with OOM. Regular [PDS 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds4&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=%3Cdefault%3E] fails as well. Sometimes timeout occurs instead of OOM. (was: Almost every time [MVCC PDS 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds4&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv] fails with OOM.) > OOM in MVCC PDS4 > - > > Key: IGNITE-11908 > URL: https://issues.apache.org/jira/browse/IGNITE-11908 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Almost every time [MVCC PDS > 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds4&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv] > fails with OOM. Regular [PDS > 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds4&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=%3Cdefault%3E] > fails as well. Sometimes timeout occurs instead of OOM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11908) OOM in MVCC PDS4
[ https://issues.apache.org/jira/browse/IGNITE-11908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reassigned IGNITE-11908: --- Assignee: (was: Ivan Pavlukhin) > OOM in MVCC PDS4 > - > > Key: IGNITE-11908 > URL: https://issues.apache.org/jira/browse/IGNITE-11908 > Project: Ignite > Issue Type: Bug > Components: mvcc >Reporter: Ivan Pavlukhin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Almost every time [MVCC PDS > 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_MvccPds4&branch_IgniteTests24Java8=%3Cdefault%3E&tab=buildTypeStatusDiv] > fails with OOM. Regular [PDS > 4|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Pds4&tab=buildTypeStatusDiv&branch_IgniteTests24Java8=%3Cdefault%3E] > fails as well. Sometimes timeout occurs instead of OOM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11910) JDBC v2: adds 'schema' to URL parameters, makes 'cache' parameter is optional for the most cases
[ https://issues.apache.org/jira/browse/IGNITE-11910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863882#comment-16863882 ] Andrew Mashenkov commented on IGNITE-11910: --- [~tledkov-gridgain] Look good, merged to master. Thanks for contribution! > JDBC v2: adds 'schema' to URL parameters, makes 'cache' parameter is optional > for the most cases > > > Key: IGNITE-11910 > URL: https://issues.apache.org/jira/browse/IGNITE-11910 > Project: Ignite > Issue Type: Bug > Components: jdbc >Reporter: Taras Ledkov >Assignee: Taras Ledkov >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > We have to do changes for the JDBC v2: > - makes 'cache' parameter is optional. > - add 'schema' parameter to URL. > When cache and schema parameters are not defined 'PUBLIC' schema is used. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11910) JDBC v2: adds 'schema' to URL parameters, makes 'cache' parameter is optional for the most cases
[
https://issues.apache.org/jira/browse/IGNITE-11910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863816#comment-16863816
]
Ignite TC Bot commented on IGNITE-11910:
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=4111539]]
{color:#d04437}Platform .NET{color} [[tests 2 TIMEOUT
|https://ci.ignite.apache.org/viewLog.html?buildId=4111538]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4111567&buildTypeId=IgniteTests24Java8_RunAll]
> JDBC v2: adds 'schema' to URL parameters, makes 'cache' parameter is optional
> for the most cases
>
>
> Key: IGNITE-11910
> URL: https://issues.apache.org/jira/browse/IGNITE-11910
> Project: Ignite
> Issue Type: Bug
> Components: jdbc
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We have to do changes for the JDBC v2:
> - makes 'cache' parameter is optional.
> - add 'schema' parameter to URL.
> When cache and schema parameters are not defined 'PUBLIC' schema is used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
