[jira] [Commented] (IGNITE-11298) TcpCommunicationSpi does not support TLSv1.3
[
https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847046#comment-16847046
]
Vitaliy Biryukov commented on IGNITE-11298:
---
[~ilyak], Yes, I'll try to fix it by the end of this week.
> TcpCommunicationSpi does not support TLSv1.3
>
>
> Key: IGNITE-11298
> URL: https://issues.apache.org/jira/browse/IGNITE-11298
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.7
>Reporter: Ilya Kasnacheev
>Assignee: Vitaliy Biryukov
>Priority: Major
> Labels: Java11
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When started on Java 11 we cannot form a secure cluster - Discovery will
> happily use the default TLSv1.3 but Communication will fail with its custom
> SSLEngine-using code.
> Need to fix that.
> Until that, nodes may be salvaged by setProtocol("TLSv1.2") on
> SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11869) control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, if user pages wasn't modified in checkpoint.
[ https://issues.apache.org/jira/browse/IGNITE-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-11869: Description: We shouldn't throw GridNotIdleException, if checkpoint contains dirty pages related to ignite-sys-cache (system background activities) only. (was: We shouldn't throw GridNotIdleException, if checkpoint contains dirty pages related to ignite-sys-cache (system background updates) only.) > control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, > if user pages wasn't modified in checkpoint. > -- > > Key: IGNITE-11869 > URL: https://issues.apache.org/jira/browse/IGNITE-11869 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > We shouldn't throw GridNotIdleException, if checkpoint contains dirty pages > related to ignite-sys-cache (system background activities) only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11592) NPE in case of continuing tx and cache stop operation.
[
https://issues.apache.org/jira/browse/IGNITE-11592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846894#comment-16846894
]
Pavel Kovalenko commented on IGNITE-11592:
--
[~zstan] Thank you for contribution. Merged to master.
> NPE in case of continuing tx and cache stop operation.
> ---
>
> Key: IGNITE-11592
> URL: https://issues.apache.org/jira/browse/IGNITE-11592
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> Parallel cache stop and tx operations may lead to NPE.
> {code}
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.CacheObjectImpl.finishUnmarshal(CacheObjectImpl.java:129)
> at
> org.apache.ignite.internal.processors.cache.transactions.TxEntryValueHolder.unmarshal(TxEntryValueHolder.java:151)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxEntry.unmarshal(IgniteTxEntry.java:964)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.unmarshal(IgniteTxHandler.java:306)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:338)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxPrepareRequest0(IgniteTxHandler.java:154)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.lambda$null$0(IgniteTxHandler.java:580)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:496)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> i hope that correct decision would be to roll back tx (on exchange phase)
> participating in stopped caches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11256) Implement read-only mode for grid
[
https://issues.apache.org/jira/browse/IGNITE-11256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846835#comment-16846835
]
Ignite TC Bot commented on IGNITE-11256:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3912465buildTypeId=IgniteTests24Java8_RunAll]
> Implement read-only mode for grid
> -
>
> Key: IGNITE-11256
> URL: https://issues.apache.org/jira/browse/IGNITE-11256
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Should be triggered from control.sh utility.
> Useful for maintenance work, for example checking partition consistency
> (idle_verify)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11869) control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, if user pages wasn't modified in checkpoint.
Sergey Antonov created IGNITE-11869: --- Summary: control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, if user pages wasn't modified in checkpoint. Key: IGNITE-11869 URL: https://issues.apache.org/jira/browse/IGNITE-11869 Project: Ignite Issue Type: Improvement Affects Versions: 2.8 Reporter: Sergey Antonov Assignee: Sergey Antonov We should throw GridNotIdleException, if checkpoint contains dirty pages related to ignite-sys-cache (system background updates) only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11869) control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, if user pages wasn't modified in checkpoint.
[ https://issues.apache.org/jira/browse/IGNITE-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-11869: Description: We shouldn't throw GridNotIdleException, if checkpoint contains dirty pages related to ignite-sys-cache (system background updates) only. (was: We should throw GridNotIdleException, if checkpoint contains dirty pages related to ignite-sys-cache (system background updates) only.) > control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, > if user pages wasn't modified in checkpoint. > -- > > Key: IGNITE-11869 > URL: https://issues.apache.org/jira/browse/IGNITE-11869 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > > We shouldn't throw GridNotIdleException, if checkpoint contains dirty pages > related to ignite-sys-cache (system background updates) only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11869) control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, if user pages wasn't modified in checkpoint.
[ https://issues.apache.org/jira/browse/IGNITE-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Antonov updated IGNITE-11869: Ignite Flags: (was: Docs Required) > control.sh idle_verify/validate_indexes shouldn't throw GridNotIdleException, > if user pages wasn't modified in checkpoint. > -- > > Key: IGNITE-11869 > URL: https://issues.apache.org/jira/browse/IGNITE-11869 > Project: Ignite > Issue Type: Improvement >Affects Versions: 2.8 >Reporter: Sergey Antonov >Assignee: Sergey Antonov >Priority: Major > > We should throw GridNotIdleException, if checkpoint contains dirty pages > related to ignite-sys-cache (system background updates) only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-11670) Java thin client: Queries are inconsistent in case of failover
[
https://issues.apache.org/jira/browse/IGNITE-11670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov reassigned IGNITE-11670:
--
Assignee: Aleksey Plekhanov
> Java thin client: Queries are inconsistent in case of failover
> --
>
> Key: IGNITE-11670
> URL: https://issues.apache.org/jira/browse/IGNITE-11670
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
>
> When a thin client does failover and switches to a new server, open cursors
> become inconsistent and silently returns the wrong result.
> Reproducer:
> {code:java}
> public void testQueryFailover() throws Exception {
> try (LocalIgniteCluster cluster = LocalIgniteCluster.start(1);
> IgniteClient client = Ignition.startClient(new
> ClientConfiguration()
> .setAddresses(cluster.clientAddresses().iterator().next()))
> ) {
> ObjectName mbeanName =
> U.makeMBeanName(Ignition.allGrids().get(0).name(), "Clients",
> ClientListenerProcessor.class.getSimpleName());
> ClientProcessorMXBean mxBean =
> MBeanServerInvocationHandler.newProxyInstance(
> ManagementFactory.getPlatformMBeanServer(), mbeanName,
> ClientProcessorMXBean.class, true);
> ClientCache cache = client.createCache("cache");
> cache.put(0, 0);
> cache.put(1, 1);
> Query> qry = new ScanQuery String>().setPageSize(1);
> try (QueryCursor> cur =
> cache.query(qry)) {
> int cnt = 0;
> for (Iterator> it =
> cur.iterator(); it.hasNext(); it.next()) {
> cnt++;
> if (cnt == 1)
> mxBean.dropAllConnections();
> }
> assertEquals(2, cnt);
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11671) Thin client: Client may hang when connected to a starting server
[
https://issues.apache.org/jira/browse/IGNITE-11671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846730#comment-16846730
]
Amelchev Nikita commented on IGNITE-11671:
--
[~alex_pl], LGTM.
> Thin client: Client may hang when connected to a starting server
>
>
> Key: IGNITE-11671
> URL: https://issues.apache.org/jira/browse/IGNITE-11671
> Project: Ignite
> Issue Type: Bug
> Components: thin client
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> If the server start process has not completed yet, but NIO listeners already
> started, the client may never get a response for the handshake request.
> Exception on the server-side:
>
> {noformat}
> [client-connector-#6416%f3b837aa-d726-46b0-a58b-8cc6267c9f96%][ClientListenerProcessor]
> Runtime error caught during grid runnable execution: GridWorker
> [name=message-received-notify,
> igniteInstanceName=f3b837aa-d726-46b0-a58b-8cc6267c9f96, finished=false,
> heartbeatTs=1554209548706, hashCode=519781823, interrupted=false,
> runner=client-connector-#6416%f3b837aa-d726-46b0-a58b-8cc6267c9f96%]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.nextConnectionId(ClientListenerNioListener.java:334)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.prepareContext(ClientListenerNioListener.java:313)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onHandshake(ClientListenerNioListener.java:251)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:132)
> at
> org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:48)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70){noformat}
>
> This happens because NIO listeners start before {{GridDiscoveryManager}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11704) Write tombstones during rebalance to get rid of deferred delete buffer
[ https://issues.apache.org/jira/browse/IGNITE-11704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov reassigned IGNITE-11704: Assignee: Maxim Muzafarov > Write tombstones during rebalance to get rid of deferred delete buffer > -- > > Key: IGNITE-11704 > URL: https://issues.apache.org/jira/browse/IGNITE-11704 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Maxim Muzafarov >Priority: Major > Labels: rebalance > > Currently Ignite relies on deferred delete buffer in order to handle > write-remove conflicts during rebalance. Given the limit size of the buffer, > this approach is fundamentally flawed, especially in case when persistence is > enabled. > I suggest to extend the logic of data storage to be able to store key > tombstones - to keep version for deleted entries. The tombstones will be > stored when rebalance is in progress and should be cleaned up when rebalance > is completed. > Later this approach may be used to implement fast partition rebalance based > on merkle trees (in this case, tombstones should be written on an incomplete > baseline). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-11091: Description: It's possible to create indexes with same name but in different cases using SqlFieldsQuery, but visor shows all indexes in upper case. So it's impossible to select which one you need. (was: Visor shows all indexes in upper case) > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > > It's possible to create indexes with same name but in different cases using > SqlFieldsQuery, but visor shows all indexes in upper case. So it's impossible > to select which one you need. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Akkuratov updated IGNITE-11091: Description: Visor shows all indexes in upper case > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > > Visor shows all indexes in upper case -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11091) Visor shows all indexes in upper case
[ https://issues.apache.org/jira/browse/IGNITE-11091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846719#comment-16846719 ] Sergey Antonov commented on IGNITE-11091: - [~iakkuratov] Please fill ticket description. Changes are looks good to me. > Visor shows all indexes in upper case > - > > Key: IGNITE-11091 > URL: https://issues.apache.org/jira/browse/IGNITE-11091 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Igor Akkuratov >Assignee: Igor Akkuratov >Priority: Minor > Fix For: 2.8 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11864) Log FileNotFoundException on restore if no segments were found.
[
https://issues.apache.org/jira/browse/IGNITE-11864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846712#comment-16846712
]
Ignite TC Bot commented on IGNITE-11864:
{panel:title=-- Run :: All: No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=3912349buildTypeId=IgniteTests24Java8_RunAll]
> Log FileNotFoundException on restore if no segments were found.
> ---
>
> Key: IGNITE-11864
> URL: https://issues.apache.org/jira/browse/IGNITE-11864
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-4696) Web Console: Create pagination control
[ https://issues.apache.org/jira/browse/IGNITE-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846688#comment-16846688 ] Vica Abramova commented on IGNITE-4696: --- [~Klaster_1] please do not forget to think about it. > Web Console: Create pagination control > -- > > Key: IGNITE-4696 > URL: https://issues.apache.org/jira/browse/IGNITE-4696 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Labels: web-console-UI-UX > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4696) Web Console: Create pagination control
[ https://issues.apache.org/jira/browse/IGNITE-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova reassigned IGNITE-4696: - Assignee: Ilya Borisov (was: Vica Abramova) > Web Console: Create pagination control > -- > > Key: IGNITE-4696 > URL: https://issues.apache.org/jira/browse/IGNITE-4696 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > Labels: web-console-UI-UX > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-4781) Web Console: Revise the Queries Screen
[ https://issues.apache.org/jira/browse/IGNITE-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova reassigned IGNITE-4781: - Assignee: Ilya Borisov (was: Vica Abramova) > Web Console: Revise the Queries Screen > -- > > Key: IGNITE-4781 > URL: https://issues.apache.org/jira/browse/IGNITE-4781 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Ilya Borisov >Priority: Major > > Mockup: https://zpl.io/adzyZ12 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-4781) Web Console: Revise the Queries Screen
[ https://issues.apache.org/jira/browse/IGNITE-4781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova updated IGNITE-4781: -- Description: Mockup: https://zpl.io/adzyZ12 > Web Console: Revise the Queries Screen > -- > > Key: IGNITE-4781 > URL: https://issues.apache.org/jira/browse/IGNITE-4781 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova >Priority: Major > > Mockup: https://zpl.io/adzyZ12 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11868) GridClient#data() should be deprecated/removed.
[
https://issues.apache.org/jira/browse/IGNITE-11868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-11868:
-
Priority: Minor (was: Major)
> GridClient#data() should be deprecated/removed.
> ---
>
> Key: IGNITE-11868
> URL: https://issues.apache.org/jira/browse/IGNITE-11868
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Vyacheslav Koptilin
>Priority: Minor
> Labels: newbie
>
> It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and
> therefore it can be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11868) GridClient#data() should be deprecated/removed.
Vyacheslav Koptilin created IGNITE-11868:
Summary: GridClient#data() should be deprecated/removed.
Key: IGNITE-11868
URL: https://issues.apache.org/jira/browse/IGNITE-11868
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Vyacheslav Koptilin
It seems that {{GridClient#data()}} does not make sense after IGNITE-3488 and
therefore it can be removed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11697) Suspended optimistic transaction automatically resumes to last thread after a timeout.
[
https://issues.apache.org/jira/browse/IGNITE-11697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846660#comment-16846660
]
Nikolay Izhikov commented on IGNITE-11697:
--
Merged to master.
[~alex_pl] Thanks for the contribution.
> Suspended optimistic transaction automatically resumes to last thread after a
> timeout.
> --
>
> Key: IGNITE-11697
> URL: https://issues.apache.org/jira/browse/IGNITE-11697
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Labels: iep-34
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This leads to unpredictable results from a user's point of view.
> Reproducer:
>
> {code:java}
> public class IgniteTxSuspendAndTimeoutTest extends GridCommonAbstractTest {
> @Test
> public void testSuspendAndTimeout() throws Exception {
> Ignite ignite = startGrid(0);
> IgniteCache cache = ignite.createCache(new
> CacheConfiguration<>().setName("c").setAtomicityMode(TRANSACTIONAL));
> Transaction tx1 = ignite.transactions().txStart(OPTIMISTIC,
> TransactionIsolation.REPEATABLE_READ, 100, 0);
> cache.put(1, 1);
> tx1.suspend();
> assertNull(cache.get(1)); // Pass here.
> doSleep(200);
> assertNull(cache.get(1)); // Fail here. But we don't expect any
> explicitly running transaction at this point.
> }
> }
> {code}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-11867) Fix flaky test GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
[
https://issues.apache.org/jira/browse/IGNITE-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov reassigned IGNITE-11867:
--
Assignee: Alexei Scherbakov
> Fix flaky test
> GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
> -
>
> Key: IGNITE-11867
> URL: https://issues.apache.org/jira/browse/IGNITE-11867
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
> {noformat}
> java.lang.AssertionError: Value for 4 is null
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingWithAsyncClearingTest.testCorrectRebalancingCurrentlyRentingPartitions(GridCacheRebalancingWithAsyncClearingTest.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2148)
> at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-4782) Web Console: Revise on-boarding behavior and user's education
[ https://issues.apache.org/jira/browse/IGNITE-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova resolved IGNITE-4782. --- Resolution: Won't Fix > Web Console: Revise on-boarding behavior and user's education > - > > Key: IGNITE-4782 > URL: https://issues.apache.org/jira/browse/IGNITE-4782 > Project: Ignite > Issue Type: Task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Vica Abramova >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11867) Fix flaky test GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
[
https://issues.apache.org/jira/browse/IGNITE-11867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-11867:
---
Description:
{noformat}
java.lang.AssertionError: Value for 4 is null
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:621)
at
org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingWithAsyncClearingTest.testCorrectRebalancingCurrentlyRentingPartitions(GridCacheRebalancingWithAsyncClearingTest.java:280)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at
org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2148)
at java.lang.Thread.run(Thread.java:748){noformat}
> Fix flaky test
> GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
> -
>
> Key: IGNITE-11867
> URL: https://issues.apache.org/jira/browse/IGNITE-11867
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
> {noformat}
> java.lang.AssertionError: Value for 4 is null
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:621)
> at
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRebalancingWithAsyncClearingTest.testCorrectRebalancingCurrentlyRentingPartitions(GridCacheRebalancingWithAsyncClearingTest.java:280)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:2148)
> at java.lang.Thread.run(Thread.java:748){noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11867) Fix flaky test GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions
Alexei Scherbakov created IGNITE-11867: -- Summary: Fix flaky test GridCacheRebalancingWithAsyncClearingTest#testCorrectRebalancingCurrentlyRentingPartitions Key: IGNITE-11867 URL: https://issues.apache.org/jira/browse/IGNITE-11867 Project: Ignite Issue Type: Bug Reporter: Alexei Scherbakov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-4936) Web Console: Improve the scroll behavior
[ https://issues.apache.org/jira/browse/IGNITE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vica Abramova resolved IGNITE-4936. --- Resolution: Done > Web Console: Improve the scroll behavior > > > Key: IGNITE-4936 > URL: https://issues.apache.org/jira/browse/IGNITE-4936 > Project: Ignite > Issue Type: Sub-task > Components: UI, wizards >Reporter: Vica Abramova >Assignee: Alexey Kuznetsov >Priority: Major > Attachments: 2.png > > > We need to finalize the tables: > # improve the scroll behavior -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11861) GridEventConsumeSelfTest.testMultithreadedWithNodeRestart fails on TC
[ https://issues.apache.org/jira/browse/IGNITE-11861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Govorukhin updated IGNITE-11861: Fix Version/s: 2.8 > GridEventConsumeSelfTest.testMultithreadedWithNodeRestart fails on TC > - > > Key: IGNITE-11861 > URL: https://issues.apache.org/jira/browse/IGNITE-11861 > Project: Ignite > Issue Type: Test >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4911099288413140059=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
