[jira] [Created] (IGNITE-13144) Add attribute methods to ClusterState enum
Sergey Antonov created IGNITE-13144:
---
Summary: Add attribute methods to ClusterState enum
Key: IGNITE-13144
URL: https://issues.apache.org/jira/browse/IGNITE-13144
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.9
We have {{boolean ClusterState#active(ClusterState)}} static method. It would
be better to have an instance method {{boolean active()}}. Also I'd like to add
methods {{boolean inactive()}} and {{boolean readOnly()}} to {{ClusterState}}
class.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13138) Add REST tests for the new cluster state change API
Sergey Antonov created IGNITE-13138: --- Summary: Add REST tests for the new cluster state change API Key: IGNITE-13138 URL: https://issues.apache.org/jira/browse/IGNITE-13138 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.9 I didn't find tests for a new REST commands introduced in an IGNITE-12225. We must fix them. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13102) IgniteCache#isClosed() returns false on server node even if the cache had closed before.
Sergey Antonov created IGNITE-13102:
---
Summary: IgniteCache#isClosed() returns false on server node even
if the cache had closed before.
Key: IGNITE-13102
URL: https://issues.apache.org/jira/browse/IGNITE-13102
Project: Ignite
Issue Type: Bug
Affects Versions: 2.8.1, 2.8
Reporter: Sergey Antonov
Fix For: 2.9
IgniteCache#isClosed() still returns {{false}} even after
{{IgniteCache#close()}}. Only server nodes affect by this problem.
Simple reproducer:
{code:java}
@Test
public void test() throws Exception {
IgniteEx node = startGrid(0);
IgniteCache cache =
node.getOrCreateCache(DEFAULT_CACHE_NAME);
assertFalse(cache.isClosed());
cache.close();
// java.lang.AssertionError
assertTrue(cache.isClosed());
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13091) Cluster read-only mode allows to create caches
Sergey Antonov created IGNITE-13091:
---
Summary: Cluster read-only mode allows to create caches
Key: IGNITE-13091
URL: https://issues.apache.org/jira/browse/IGNITE-13091
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9
Reporter: Sergey Antonov
Fix For: 2.9
You can create a cache if cluster in a read-only mode.
See {{CacheCreateDestroyClusterReadOnlyModeTest#testCacheCreateDenied}} test.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13079) Replace deprecated cluster activation methods in tests.
Sergey Antonov created IGNITE-13079:
---
Summary: Replace deprecated cluster activation methods in tests.
Key: IGNITE-13079
URL: https://issues.apache.org/jira/browse/IGNITE-13079
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
After we IGNITE-12225 we have a new API for a changing cluster state. We must
replace deprecated methods ({{IgniteCluster#active()}},
{{IgniteCluster#active(boolean)}} and etc) to a new API
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13076) Cluster read-only mode doesn't affect LOCAL caches
Sergey Antonov created IGNITE-13076:
---
Summary: Cluster read-only mode doesn't affect LOCAL caches
Key: IGNITE-13076
URL: https://issues.apache.org/jira/browse/IGNITE-13076
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9
Reporter: Sergey Antonov
Fix For: 2.9
You can make data modification operations with LOCAL cache even if cluster in a
{{ACTIVE_READ_ONLY}} state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13071) Improve test coverage for read-only cluster state
Sergey Antonov created IGNITE-13071: --- Summary: Improve test coverage for read-only cluster state Key: IGNITE-13071 URL: https://issues.apache.org/jira/browse/IGNITE-13071 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.9 It would be nice to extend test coverage for this feature. We don't have tests for: * data structures * cache destroy/create * cache clear * DDL requests * Cache updates from task/deployed service -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13047) Ignite node must return Ignition#KILL_EXIT_CODE exit code, if node had stopped by StopNodeFailureHandler or StopNodeOrHaltFailureHandler
Sergey Antonov created IGNITE-13047: --- Summary: Ignite node must return Ignition#KILL_EXIT_CODE exit code, if node had stopped by StopNodeFailureHandler or StopNodeOrHaltFailureHandler Key: IGNITE-13047 URL: https://issues.apache.org/jira/browse/IGNITE-13047 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Ignite process must be finished with exit code 130 [1] if the node had stopped by StopNodeFailureHandler or StopNodeOrHaltFailureHanlder. [1] https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/Ignition.html#KILL_EXIT_CODE -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13004) Fix wrong comparison in TcpCommunicationSpi#closeConnections(UUID)
Sergey Antonov created IGNITE-13004:
---
Summary: Fix wrong comparison in
TcpCommunicationSpi#closeConnections(UUID)
Key: IGNITE-13004
URL: https://issues.apache.org/jira/browse/IGNITE-13004
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9, 2.8.1
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.9
In IGNITE-12774 was introduced a bug in comparison:
{code:java}
for (ConnectionKey connKey : clientFuts.keySet()) {
if (!nodeId.equals(connKey))
continue;
{code}
The right code is:
{code:java}
for (ConnectionKey connKey : clientFuts.keySet()) {
if (!nodeId.equals(connKey.nodeId()))
continue;
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12985) Fix unguarded log.info/log.debug/log.trace usages
Sergey Antonov created IGNITE-12985:
---
Summary: Fix unguarded log.info/log.debug/log.trace usages
Key: IGNITE-12985
URL: https://issues.apache.org/jira/browse/IGNITE-12985
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov
There are multiple places in code where {{log.info()/log.debug()/log.trace()}}
is called without checking {{if (log.isInfoEnabled)}}. This leads to polluted
logs when INFO/DEBUG/TRACE is disabled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12955) Document a new command control.sh --cache check_index_inline_sizes
Sergey Antonov created IGNITE-12955: --- Summary: Document a new command control.sh --cache check_index_inline_sizes Key: IGNITE-12955 URL: https://issues.apache.org/jira/browse/IGNITE-12955 Project: Ignite Issue Type: New Feature Components: documentation Reporter: Sergey Antonov Fix For: 2.9 Please look at IGNITE-12942 and devlist discussion linked to IGNITE-12942 for all information. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12942) control.sh add command for checking that inline size is same on all cluster nodes
Sergey Antonov created IGNITE-12942: --- Summary: control.sh add command for checking that inline size is same on all cluster nodes Key: IGNITE-12942 URL: https://issues.apache.org/jira/browse/IGNITE-12942 Project: Ignite Issue Type: New Feature Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.9 We should check that the inline size is the same for the index on all nodes in the cluster. 1. Check inline_size of secondary indexes on node join. Warn to log if they differ and propose a recreate problem index. 2. Introduce a new command to control.sh (control.sh --cache check_index_inline_sizes). The command will check inline sizes of secondary indexes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12803) Investigate exception message on too many open files in different OS.
Sergey Antonov created IGNITE-12803: --- Summary: Investigate exception message on too many open files in different OS. Key: IGNITE-12803 URL: https://issues.apache.org/jira/browse/IGNITE-12803 Project: Ignite Issue Type: Task Environment: In IGNITE-12774 we introduced node failing if we got "too many open files" during open connection. I'm not sure that in all OS we will get that message. We need to investigate it. Reporter: Sergey Antonov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12774) Transaction hungs after too many open files NIO exception
Sergey Antonov created IGNITE-12774:
---
Summary: Transaction hungs after too many open files NIO exception
Key: IGNITE-12774
URL: https://issues.apache.org/jira/browse/IGNITE-12774
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Transaction hung after “Open too many files” error and never been finished.
{code:java}
import java.net.SocketException;
import java.util.concurrent.atomic.AtomicBoolean;
import org.apache.ignite.cluster.ClusterNode;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.failure.StopNodeOrHaltFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.lang.IgniteInClosure;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.spi.IgniteSpiException;
import org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheMode.PARTITIONED;
public class TooManyOpenFilesTest extends GridCommonAbstractTest {
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
return super.getConfiguration(igniteInstanceName)
.setFailureHandler(new StopNodeOrHaltFailureHandler())
.setCommunicationSpi(new TooManyOpenFilesTcpCommunicationSpi())
.setConsistentId(igniteInstanceName);
}
@Override protected void beforeTest() throws Exception {
super.beforeTest();
stopAllGrids();
cleanPersistenceDir();
}
@Override protected void afterTest() throws Exception {
stopAllGrids();
cleanPersistenceDir();
super.afterTest();
}
public void test() throws Exception {
IgniteEx crd = startGrids(3);
crd.cluster().active(true);
crd.getOrCreateCache(new
CacheConfiguration<>().setName(DEFAULT_CACHE_NAME).setAtomicityMode(TRANSACTIONAL).setBackups(1).setCacheMode(PARTITIONED));
TooManyOpenFilesTcpCommunicationSpi spi =
(TooManyOpenFilesTcpCommunicationSpi)grid(2).context().config().getCommunicationSpi();
try (Transaction tx =
grid(1).transactions().txStart(TransactionConcurrency.PESSIMISTIC,
TransactionIsolation.REPEATABLE_READ)) {
IgniteCache cache =
grid(1).cache(DEFAULT_CACHE_NAME);
cache.put(1, 1);
spi.throwException.set(true);
cache.put(2, 2);
cache.put(3, 2);
cache.put(4, 2);
// hungs here.
tx.commit();
}
for (int i=0; i < 3 ; i++) {
assertEquals(1, grid(i).cache(DEFAULT_CACHE_NAME).get(1));
assertEquals(2, grid(i).cache(DEFAULT_CACHE_NAME).get(2));
}
}
private static class TooManyOpenFilesTcpCommunicationSpi extends
TcpCommunicationSpi {
private final AtomicBoolean throwException = new AtomicBoolean();
/** {@inheritDoc} */
@Override public void sendMessage(ClusterNode node, Message msg) throws
IgniteSpiException {
if (throwException.get())
throw getException(node);
super.sendMessage(node, msg);
}
/** {@inheritDoc} */
@Override public void sendMessage(
ClusterNode node,
Message msg,
IgniteInClosure ackC
) throws IgniteSpiException {
if (throwException.get())
throw getException(node);
super.sendMessage(node, msg, ackC);
}
private IgniteSpiException getException(ClusterNode node) {
String checkedExceptionMsg = "Failed to connect to node (is node
still alive?). " +
"Make sure that each ComputeTask and cache Transaction has a
timeout set " +
"in order to prevent parties from waiting forever in case of
network issues " +
"[nodeId=" + node.id() + ", addrs=null]";
return new IgniteSpiException("Failed to send message to remote
node: " + node.id(), new IgniteCheckedException(checkedExceptionMsg, new
SocketException("Too many open files")));
}
}
}
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12710) Extension log in rebuild indexes to search problems
Sergey Antonov created IGNITE-12710: --- Summary: Extension log in rebuild indexes to search problems Key: IGNITE-12710 URL: https://issues.apache.org/jira/browse/IGNITE-12710 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.9 We should have the ability to get extended information about rebuild indexes: cache, cache id, cache group, cache group id, index name, index type, index size. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12520) Wrong year in copyright in correct output of control utility.
Sergey Antonov created IGNITE-12520: --- Summary: Wrong year in copyright in correct output of control utility. Key: IGNITE-12520 URL: https://issues.apache.org/jira/browse/IGNITE-12520 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12225) Add enum for cluster state
Sergey Antonov created IGNITE-12225:
---
Summary: Add enum for cluster state
Key: IGNITE-12225
URL: https://issues.apache.org/jira/browse/IGNITE-12225
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
We have 3 cluster states at the moment: inactive, active, read-only.
For getting current cluster state and changing them {{IgniteCluster}} has
methods:
* {{boolean active()}}, {{void active(boolean active)}} - for cluster
activation/deactivation
* {{boolean readOnly()}}, {{void readOnly(boolean readOnly)}} - for
enabling/disabling read-only mode.
Also we have control.sh commans for changing cluster state:
* {{--activate}}
* {{--deactivate}}
* {{--read-only-on}}
* {{--read-only-off}}
For me current API looks unuseful. My proposal:
# Create enum {{ClusterState}} with values {{ACTIVE}}, {{INACTIVE}},
{{READ-ONLY}}.
# Add methods to {{IgniteCluster}}:
## {{ClusterState state()}} returns current cluster state
## {{void state(ClusterState newState)}} changes cluster state to {{newState}}
state
## Mark as deprecated the following methods in {{IgniteCluster}}: {{boolean
active()}}, {{void active(boolean active)}},
## Add new command to control.sh: {{control.sh --set-state
(ACTIVE|INACTIVE|READ-ONLY)}}
## Add warn message that command is depricated in control.sh. Commands:
{{--activate}}, {{--deactivate}}, {{--read-only-on}}, {{--read-only-off}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12153) Control.sh add test for checking that help and cache help output are not broken.
Sergey Antonov created IGNITE-12153: --- Summary: Control.sh add test for checking that help and cache help output are not broken. Key: IGNITE-12153 URL: https://issues.apache.org/jira/browse/IGNITE-12153 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 We should store "ideal" outputs in resorces and compare with current. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12136) Test ClusterReadOnlyModeTest is flaky.
Sergey Antonov created IGNITE-12136: --- Summary: Test ClusterReadOnlyModeTest is flaky. Key: IGNITE-12136 URL: https://issues.apache.org/jira/browse/IGNITE-12136 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4535823271211432266=testDetails_IgniteTests24Java8=%3Cdefault%3E -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (IGNITE-12125) Concurrency problem in PagesWriteThrottle
Sergey Antonov created IGNITE-12125:
---
Summary: Concurrency problem in PagesWriteThrottle
Key: IGNITE-12125
URL: https://issues.apache.org/jira/browse/IGNITE-12125
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
In IGNITE-12006 and IGNITE-9231 were added code:
{code}
parkThrds.forEach(LockSupport::unpark);
parkThrds.clear();
{code}
This code isn't thread-safe. We should remove from {{parkThrds}} only unparked
threads.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (IGNITE-12052) GridDhtTxPrepareFuture should print transaction in case of assertion error
Sergey Antonov created IGNITE-12052:
---
Summary: GridDhtTxPrepareFuture should print transaction in case
of assertion error
Key: IGNITE-12052
URL: https://issues.apache.org/jira/browse/IGNITE-12052
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
At the moment we getting exception, if assertion error occurs:
{noformat}
2019-07-13
20:23:00.769[ERROR][srvc-deploy-#299%xxx_GRID%xxxGridNodeName%][o.a.i.i.p.s.GridServiceProcessor]
Error when executing service: null
java.lang.AssertionError: Got removed exception on entry with dht local
candidate: IgniteTxEntry []
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.sendPrepareRequests(GridDhtTxPrepareFuture.java:1368)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1276)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.access$000(GridDhtTxPrepareFuture.java:109)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture$2.apply(GridDhtTxPrepareFuture.java:704)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture$2.apply(GridDhtTxPrepareFuture.java:699)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onDone(GridDhtForceKeysFuture.java:153)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.onDone(GridDhtForceKeysFuture.java:69)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:285)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.markInitialized(GridCompoundFuture.java:276)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtForceKeysFuture.init(GridDhtForceKeysFuture.java:217)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$2.apply(GridDhtPreloader.java:523)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$2.apply(GridDhtPreloader.java:521)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.checkComplete(GridCompoundFuture.java:285)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:144)
at
org.apache.ignite.internal.util.future.GridCompoundFuture.apply(GridCompoundFuture.java:45)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture.onDone(GridAffinityAssignmentCache.java:850)
at
org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache$AffinityReadyFuture.onDone(GridAffinityAssignmentCache.java:834)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:451)
at
[jira] [Created] (IGNITE-12006) Threads may be parked for indefinite time during throttling after spurious wakeups
Sergey Antonov created IGNITE-12006:
---
Summary: Threads may be parked for indefinite time during
throttling after spurious wakeups
Key: IGNITE-12006
URL: https://issues.apache.org/jira/browse/IGNITE-12006
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Assignee: Sergey Antonov
In the log we see the following behavior:
{noformat}
2019-07-04 06:29:03.649[WARN
][sys-#328%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#328%NODE%xyzGridNodeName% for timeout(ms)=16335
2019-07-04 06:29:03.649[WARN
][sys-#326%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#326%NODE%xyzGridNodeName% for timeout(ms)=13438
2019-07-04 06:29:03.649[WARN
][sys-#277%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#277%NODE%xyzGridNodeName% for timeout(ms)=11609
2019-07-04 06:29:03.649[WARN
][sys-#331%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#331%NODE%xyzGridNodeName% for timeout(ms)=18009
2019-07-04 06:29:03.649[WARN
][sys-#321%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#321%NODE%xyzGridNodeName% for timeout(ms)=15557
2019-07-04 06:29:03.650[WARN
][sys-#307%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#307%NODE%xyzGridNodeName% for timeout(ms)=27938
2019-07-04 06:29:03.649[WARN
][sys-#316%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#316%NODE%xyzGridNodeName% for timeout(ms)=12189
2019-07-04 06:29:03.649[WARN
][sys-#311%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#311%NODE%xyzGridNodeName% for timeout(ms)=11056
2019-07-04 06:29:03.650[WARN
][sys-#295%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#295%NODE%xyzGridNodeName% for timeout(ms)=20848
2019-07-04 06:29:03.649[WARN
][sys-#290%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#290%NODE%xyzGridNodeName% for timeout(ms)=14816
2019-07-04 06:29:03.649[WARN
][sys-#332%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#332%NODE%xyzGridNodeName% for timeout(ms)=14110
2019-07-04 06:29:03.649[WARN
][sys-#298%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#298%NODE%xyzGridNodeName% for timeout(ms)=10028
2019-07-04 06:29:03.650[WARN
][sys-#304%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#304%NODE%xyzGridNodeName% for timeout(ms)=19855
2019-07-04 06:29:03.650[WARN
][sys-#331%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#331%NODE%xyzGridNodeName% for timeout(ms)=41277
2019-07-04 06:29:03.650[WARN
][sys-#291%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#291%NODE%xyzGridNodeName% for timeout(ms)=17151
2019-07-04 06:29:03.650[WARN
][sys-#308%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#308%NODE%xyzGridNodeName% for timeout(ms)=39312
2019-07-04 06:29:03.650[WARN
][sys-#322%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#322%NODE%xyzGridNodeName% for timeout(ms)=43341
2019-07-04 06:29:03.650[WARN
][sys-#306%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#306%NODE%xyzGridNodeName% for timeout(ms)=21890
2019-07-04 06:29:03.650[WARN
][sys-#315%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#315%NODE%xyzGridNodeName% for timeout(ms)=18909
2019-07-04 06:29:03.650[WARN
][sys-#321%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#321%NODE%xyzGridNodeName% for timeout(ms)=74129
2019-07-04 06:29:03.650[WARN
][sys-#305%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#305%NODE%xyzGridNodeName% for timeout(ms)=26608
2019-07-04 06:29:03.650[WARN
][sys-#309%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#309%NODE%xyzGridNodeName% for timeout(ms)=77835
2019-07-04 06:29:03.650[WARN
][sys-#291%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#291%NODE%xyzGridNodeName% for timeout(ms)=90104
2019-07-04 06:29:03.650[WARN
][sys-#325%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#325%NODE%xyzGridNodeName% for timeout(ms)=85813
2019-07-04 06:29:03.650[WARN
][sys-#314%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#314%NODE%xyzGridNodeName% for timeout(ms)=81727
2019-07-04 06:29:03.650[WARN
][sys-#338%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl] Parking
thread=sys-#338%NODE%xyzGridNodeName% for timeout(ms)=99340
2019-07-04 06:29:03.650[WARN
[jira] [Created] (IGNITE-11889) Add security permissions cluster state change operations
Sergey Antonov created IGNITE-11889: --- Summary: Add security permissions cluster state change operations Key: IGNITE-11889 URL: https://issues.apache.org/jira/browse/IGNITE-11889 Project: Ignite Issue Type: Bug Components: security Reporter: Sergey Antonov We should add security permissions for cluster state change operations: * Cluster activation/deactivation. * Set/change baseline topology. * Enable/disable read-only mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11876) control.sh idle verify --cache-filter doesn't work without --dump option
Sergey Antonov created IGNITE-11876:
---
Summary: control.sh idle verify --cache-filter doesn't work
without --dump option
Key: IGNITE-11876
URL: https://issues.apache.org/jira/browse/IGNITE-11876
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
At this moment control.sh {{--cache idle_verify --cache-filter PERSISTENT}}
doesn't work (see {{VerifyBackupPartitionsTaskV2#isCacheMatchFilter()}}). We
should fix it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11866) Add ability to activate cluster in read-only mode
Sergey Antonov created IGNITE-11866: --- Summary: Add ability to activate cluster in read-only mode Key: IGNITE-11866 URL: https://issues.apache.org/jira/browse/IGNITE-11866 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov After IGNITE-11256 we have cluster read-only mode. We should have ability to activate cluster and enable read-only mode like atomic operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11863) .NET: Add clurster read-only mode API (status, run-time change)
Sergey Antonov created IGNITE-11863: --- Summary: .NET: Add clurster read-only mode API (status, run-time change) Key: IGNITE-11863 URL: https://issues.apache.org/jira/browse/IGNITE-11863 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Sergey Antonov We would introduce at IGNITE-11256 new methods in IgniteCluster. We need their support in .Net side. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11859) CommandHandlerParsingTest#testExperimentalCommandIsDisabled() don't works
Sergey Antonov created IGNITE-11859:
---
Summary:
CommandHandlerParsingTest#testExperimentalCommandIsDisabled() don't works
Key: IGNITE-11859
URL: https://issues.apache.org/jira/browse/IGNITE-11859
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Fix For: 2.8
{{parseArgs(Arrays.asList(WAL.text(), WAL_PRINT));}} and
{{parseArgs(Arrays.asList(WAL.text(), WAL_DELETE));}} should throw
IllegalArgumentException, but it isn't.
h2. How to reproduce:
Replace test to:
{code:java}
/**
* Test that experimental command (i.e. WAL command) is disabled by default.
*/
@Test
public void testExperimentalCommandIsDisabled() {
System.clearProperty(IGNITE_ENABLE_EXPERIMENTAL_COMMAND);
GridTestUtils.assertThrows(null,
()->parseArgs(Arrays.asList(WAL.text(), WAL_PRINT)),
IllegalArgumentException.class, null);
GridTestUtils.assertThrows(null,
()->parseArgs(Arrays.asList(WAL.text(), WAL_DELETE)),
IllegalArgumentException.class, null);
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11814) Log finish rebuilding all indexes
Sergey Antonov created IGNITE-11814:
---
Summary: Log finish rebuilding all indexes
Key: IGNITE-11814
URL: https://issues.apache.org/jira/browse/IGNITE-11814
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
For detecting finish of rebuilding all indexes we should find in logs all
messages:
1) {{Started indexes rebuilding for cache [name=}}
2) {{Finished indexes rebuilding for cache [name=}}
3) {{Failed to rebuild indexes for cache [name=}}
And check, that number of messages (1) equal sum of number of messages (2) and
(3).
We should log message about finish rebuilding indexes for all caches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11812) control.sh ignores quotes in passed arguments
Sergey Antonov created IGNITE-11812:
---
Summary: control.sh ignores quotes in passed arguments
Key: IGNITE-11812
URL: https://issues.apache.org/jira/browse/IGNITE-11812
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Fix For: 2.8
Control.sh should consider quotes in incoming arguments. i.e. I expect that
{{control.sh --baseline set "p1,p2,p3","p4,p5,p6" --yes}} set BLT with two
nodes with consistent ids: {{p1,p2,p3}} and {{p4,p5,p6}}, but now it tries to
set BLT with six nodes {{p1}}, {{p2}}, {{p3}}, {{p4}}, {{p5}}, {{p6}}
Reproducer. (Add this test to {{CommandHandlerParsingTest}})
{code:java}
@Test
public void testQuotesWillNotIgnored() throws Exception {
CommandHandler hnd = new CommandHandler();
Arguments args = hnd.parseAndValidate(
Arrays.asList(
BASELINE.text(),
BaselineCommand.SET.text(),
"\"1,2,3\",\"3,2,1\""
)
);
assertEquals(BASELINE, args.command());
assertEquals(BaselineCommand.SET, args.baselineArguments().getCmd());
// FIx me: expected 2, actual 6
assertEquals(2, args.baselineArguments().getConsistentIds().size());
assertEquals("1,2,3",
args.baselineArguments().getConsistentIds().get(0));
assertEquals("3,2,1",
args.baselineArguments().getConsistentIds().get(1));
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11809) Missing help for control.sh --baseline collect command.
Sergey Antonov created IGNITE-11809:
---
Summary: Missing help for control.sh --baseline collect command.
Key: IGNITE-11809
URL: https://issues.apache.org/jira/browse/IGNITE-11809
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
I found enum value {{BaselineCommand#COLLECT}}, but I don't see this option in
help output. We should add example with {{BaselineCommand#COLLECT}} to
{{control.sh --help output}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11795) JDBC thin datastreamer don't throws exception is case of problems on closing streamer.
Sergey Antonov created IGNITE-11795: --- Summary: JDBC thin datastreamer don't throws exception is case of problems on closing streamer. Key: IGNITE-11795 URL: https://issues.apache.org/jira/browse/IGNITE-11795 Project: Ignite Issue Type: Bug Components: jdbc, thin client Reporter: Sergey Antonov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11784) Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
Sergey Antonov created IGNITE-11784:
---
Summary: Replace TcpDiscoveryNode to nodeId in TcpDiscoveryMessages
Key: IGNITE-11784
URL: https://issues.apache.org/jira/browse/IGNITE-11784
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Fix For: 2.8
{{TcpDiscoveryDuplicateIdMessage}} and {{TcpDiscoveryStatusCheckMessage}} have
TcpDiscoveryNode filed. TcpDiscoveryNode could be huge object due to node
attributes. We could sent only nodeId and get TcpDiscoveryNode from DiscoCache
on target node.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11753) control.sh improve error message in case of connection to secured cluster without credentials.
Sergey Antonov created IGNITE-11753:
---
Summary: control.sh improve error message in case of connection to
secured cluster without credentials.
Key: IGNITE-11753
URL: https://issues.apache.org/jira/browse/IGNITE-11753
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
If control.sh tries to connect to secured cluster without login/password now we
got:
{noformat}
./control.sh --state
Failed to get cluster state.
Authentication error, try connection again.
user:
{noformat}
We should print info about attempt to connect to secured cluster and request
login/password if it isn't set. I.e.
{noformat}
./control.sh --state
Failed to get cluster state.
Cluster required authentication.
user:
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11719) Document cluster read-only mode
Sergey Antonov created IGNITE-11719: --- Summary: Document cluster read-only mode Key: IGNITE-11719 URL: https://issues.apache.org/jira/browse/IGNITE-11719 Project: Ignite Issue Type: New Feature Components: documentation Reporter: Sergey Antonov Assignee: Artem Budnikov Fix For: 2.8 We should document cluster wide read-only mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11631) Server node with PDS and SSL fails on start with NPE
Sergey Antonov created IGNITE-11631:
---
Summary: Server node with PDS and SSL fails on start with NPE
Key: IGNITE-11631
URL: https://issues.apache.org/jira/browse/IGNITE-11631
Project: Ignite
Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
Server node fails with NPE, if persistence and SSL are enable.
Stacktrace:
{code:java}
java.lang.NullPointerException
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.createSocket(TcpDiscoverySpi.java:1565)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1503)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1309)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1144)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:957)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:422)
at
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2089)
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:940)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1743)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1085)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1992)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1683)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1109)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:607)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:984)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:925)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:913)
at
org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:879)
at
org.apache.ignite.testframework.junits.GridAbstractTest$4.call(GridAbstractTest.java:822)
at
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:84)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11536) Add information about possible long GC pause to checkpoint started message.
Sergey Antonov created IGNITE-11536:
---
Summary: Add information about possible long GC pause to
checkpoint started message.
Key: IGNITE-11536
URL: https://issues.apache.org/jira/browse/IGNITE-11536
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
One of possible reasons long hold of write lock on checkpoint is GC pause. Now
you must check logs around on {{Possible too long JVM pause}} message. We
should print possible long GC pause time in {{Checkpoint started}} message, if
threshhold was passed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11225) Control.sh add ability to fail node manualy
Sergey Antonov created IGNITE-11225:
---
Summary: Control.sh add ability to fail node manualy
Key: IGNITE-11225
URL: https://issues.apache.org/jira/browse/IGNITE-11225
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Fix For: 2.8
We should have ability to fail node manualy, for example by control.sh utility.
I think invocation on coordinator {{DiscoverySpi#failNone()}} will be enough.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11178) TcpDiscovertySpi. Print real wait time for timeout exception.
Sergey Antonov created IGNITE-11178: --- Summary: TcpDiscovertySpi. Print real wait time for timeout exception. Key: IGNITE-11178 URL: https://issues.apache.org/jira/browse/IGNITE-11178 Project: Ignite Issue Type: Improvement Affects Versions: 2.7 Reporter: Sergey Antonov Fix For: 2.8 We should print to log real wait time in TcpDiscoverySpi in case of timeout exception occurred. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11161) ClientCache get by user defined key returns null
Sergey Antonov created IGNITE-11161:
---
Summary: ClientCache get by user defined key returns null
Key: IGNITE-11161
URL: https://issues.apache.org/jira/browse/IGNITE-11161
Project: Ignite
Issue Type: Bug
Components: thin client
Affects Versions: 2.7
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
Scenario:
* Start server node with predefined cache and activate cluster.
* Connect thin java client to cluster
* Put entry to the cache with user defined key (custom class) from server node.
* Try get value from thin client by the same key.
Expected:
* Returns putted value
Actual:
* Returns null
Reproducer:
{code:java}
import java.util.Objects;
import org.apache.ignite.Ignition;
import org.apache.ignite.client.IgniteClient;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.ClientConfiguration;
import org.apache.ignite.configuration.ClientConnectorConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.util.typedef.internal.S;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.junit.runners.JUnit4;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
@RunWith(JUnit4.class)
public class ClientTestGet extends GridCommonAbstractTest {
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
return super.getConfiguration(igniteInstanceName)
.setClientConnectorConfiguration(new ClientConnectorConfiguration())
.setDataStorageConfiguration(new DataStorageConfiguration())
.setCacheConfiguration(new
CacheConfiguration().setName(DEFAULT_CACHE_NAME).setWriteSynchronizationMode(FULL_SYNC));
}
@Override protected void beforeTest() throws Exception {
super.beforeTest();
cleanPersistenceDir();
}
@Test
public void testGet() throws Exception {
IgniteConfiguration serverCfg = getConfiguration("server");
IgniteEx server = startGrid(serverCfg);
server.cluster().active(true);
IgniteClient client = Ignition.startClient(
new ClientConfiguration().setAddresses("127.0.0.1:" +
serverCfg.getClientConnectorConfiguration().getPort())
);
server.cache(DEFAULT_CACHE_NAME).put(new Key(0), 0);
Object serverVal = server.cache(DEFAULT_CACHE_NAME).get(new Key(0));
Object clientVal = client.cache(DEFAULT_CACHE_NAME).get(new Key(0));
assertEquals(serverVal, clientVal);
}
private static class Key {
private final int i;
private Key(int i) {
this.i = i;
}
/** {@inheritDoc} */
@Override public boolean equals(Object o) {
if (this == o)
return true;
if (o == null || getClass() != o.getClass())
return false;
return i == ((Key)o).i;
}
/** {@inheritDoc} */
@Override public int hashCode() {
return Objects.hash(i);
}
/** {@inheritDoc} */
@Override public String toString() {
return S.toString(Key.class, this);
}
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11149) Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc
Sergey Antonov created IGNITE-11149: --- Summary: Update default value for IGNITE_DISABLE_WAL_DURING_REBALANCING in javadoc Key: IGNITE-11149 URL: https://issues.apache.org/jira/browse/IGNITE-11149 Project: Ignite Issue Type: Bug Components: documentation Reporter: Sergey Antonov After IGNITE-10505 default value of IGNITE_DISABLE_WAL_DURING_REBALANCING was changed from false to true. But javadoc wasn't updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11147) Dynamic cache start during rebalance leads to start rebalance for all cache groups in case of IGNITE_DISABLE_WAL_DURING_REBALANCING = true
Sergey Antonov created IGNITE-11147: --- Summary: Dynamic cache start during rebalance leads to start rebalance for all cache groups in case of IGNITE_DISABLE_WAL_DURING_REBALANCING = true Key: IGNITE-11147 URL: https://issues.apache.org/jira/browse/IGNITE-11147 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7 Reporter: Sergey Antonov Fix For: 2.8 Scenario: 1) Start cluster with PDS and option (IGNITE_DISABLE_WAL_DURING_REBALANCING = true). Activate cluster and start few dinymic caches. 2) Stop one node and clean its PDS. 3) Start the node again. It's come back to the cluster. Rebalance started. 4) During rebalance start some caches (part of them should be already started on nodes). Expected: Rebalance will be started only for new caches. For other nodes rebalance willn't canceled. Actual: Rebalance wiil be canceled and starts again for all cache groups (including rebalanced yet) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11142) Control.sh should print detailed information about passed transaction.
Sergey Antonov created IGNITE-11142:
---
Summary: Control.sh should print detailed information about passed
transaction.
Key: IGNITE-11142
URL: https://issues.apache.org/jira/browse/IGNITE-11142
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Fix For: 2.8
We should be able to get detailed information about transactions. Approximate
info per node:
* Transaction state
* Used caches
* Used entry keys
* Locked keys
Possible command: {{control.sh --tx-info --ids txid1[txid2,...txidN]}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11092) CacheInterceptor add callbacks for binary objects
Sergey Antonov created IGNITE-11092:
---
Summary: CacheInterceptor add callbacks for binary objects
Key: IGNITE-11092
URL: https://issues.apache.org/jira/browse/IGNITE-11092
Project: Ignite
Issue Type: Improvement
Components: cache
Reporter: Sergey Antonov
Fix For: 3.0
Current API of cache interceptor difficult for use. You should implements
interface with Object, Object class parameters and use {{if (o instance of
BinaryObject)}} in each method, if you work with cache in both modes: binary
and object.
Possible names of new methods:
* onBinaryGet()
* onBeforeBinaryUpdate()/onAfterBinaryUpdate()
* onBeforeBinaryRemove()/onAfterBinaryRemove()
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11077) Add information about SSL cipher suites to apacheignite.readme.io
Sergey Antonov created IGNITE-11077: --- Summary: Add information about SSL cipher suites to apacheignite.readme.io Key: IGNITE-11077 URL: https://issues.apache.org/jira/browse/IGNITE-11077 Project: Ignite Issue Type: Task Components: documentation Reporter: Sergey Antonov I didn't find information about ssl cipher suites on https://apacheignite.readme.io/docs/ssltls -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11076) Add documentation for control.sh idle_verify --exclude-caches
Sergey Antonov created IGNITE-11076:
---
Summary: Add documentation for control.sh idle_verify
--exclude-caches
Key: IGNITE-11076
URL: https://issues.apache.org/jira/browse/IGNITE-11076
Project: Ignite
Issue Type: Task
Components: documentation
Reporter: Sergey Antonov
Assignee: Artem Budnikov
Fix For: 2.8
control.sh cache --help output
{noformat}
The '--cache subcommand' is used to get information about and perform actions
with caches. The command has the following syntax:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
[--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ..., SSL_PROTOCOL_N]]
[--ssl-cipher-suites SSL_CIPHER_1[, SSL_CIPHER_2, ..., SSL_CIPHER_N]]
[--ssl-key-algorithm SSL_KEY_ALGORITHM] [--keystore-type KEYSTORE_TYPE]
[--keystore KEYSTORE_PATH] [--keystore-password KEYSTORE_PASSWORD]
[--truststore-type TRUSTSTORE_TYPE] [--truststore TRUSTSTORE_PATH]
[--truststore-password TRUSTSTORE_PASSWORD] --cache [subcommand]
The subcommands that take [nodeId] as an argument ('list', 'contention' and
'validate_indexes') will be executed on the given node or on all server nodes
if the option is not specified. Other commands will run on a random server node.
Subcommands:
--cache list regexPattern [--groups|--seq] [nodeId] [--config] [--output-format
multi-line]
Show information about caches, groups or sequences that match a regular
expression. When executed without parameters, this subcommand prints the list
of caches.
Parameters:
--config - print all configuration parameters for each cache.
--output-format multi-line - print configuration parameters per line. This
option has effect only when used with --config and without [--groups|--seq].
--groups - print information about groups.
--seq - print information about sequences.
--cache contention minQueueSize [nodeId] [maxPrint]
Show the keys that are point of contention for multiple transactions.
--cache idle_verify [--dump] [--skip-zeros] [--check-crc] [(--exclude-caches
cacheName1,...,cacheNameN)|(--cache-filter
ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT)|cacheName1,...,cacheNameN]
Verify counters and hash sums of primary and backup partitions for the
specified caches on an idle cluster and print out the differences, if any.
Parameters:
--check-crc - check the CRC-sum of pages stored on disk before verifying data
consistency in partitions between primary and backup nodes.
--cache validate_indexes [cacheName1,...,cacheNameN] [nodeId] [--check-first
N|--check-through K]
Validate indexes on an idle cluster and print out the keys that are missing in
the indexes.
Parameters:
--check-first N - validate only the first N keys
--check-through K - validate every Kth key
--cache distribution nodeId|null [cacheName1,...,cacheNameN] [--user-attributes
attrName1,...,attrNameN]
Prints the information about partition distribution.
--cache reset_lost_partitions cacheName1,...,cacheNameN
Reset the state of lost partitions for the specified caches.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11060) Add documentation about CacheInterceptor.
Sergey Antonov created IGNITE-11060: --- Summary: Add documentation about CacheInterceptor. Key: IGNITE-11060 URL: https://issues.apache.org/jira/browse/IGNITE-11060 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Sergey Antonov Assignee: Artem Budnikov Fix For: 2.8 I didn't find documentation about CacheInterceptor in [https://apacheignite.readme.io/] (search request [https://apacheignite.readme.io/v2.7/search?q=interceptor] ) I think we should document this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11047) Control.sh replace extendable class for TaskArg classes from VisorDataTransferObject to IgniteDataTransferObject
Sergey Antonov created IGNITE-11047: --- Summary: Control.sh replace extendable class for TaskArg classes from VisorDataTransferObject to IgniteDataTransferObject Key: IGNITE-11047 URL: https://issues.apache.org/jira/browse/IGNITE-11047 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 3.0 VisorDataTransferObject is deprecated. We should use IgniteDataTransferObject instead of. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11046) Move control.sh utility to separate module
Sergey Antonov created IGNITE-11046: --- Summary: Move control.sh utility to separate module Key: IGNITE-11046 URL: https://issues.apache.org/jira/browse/IGNITE-11046 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 3.0 We should move utility from ignite-core module. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11045) Rework control.sh utility
Sergey Antonov created IGNITE-11045: --- Summary: Rework control.sh utility Key: IGNITE-11045 URL: https://issues.apache.org/jira/browse/IGNITE-11045 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 3.0 It's ubmrella ticket for all improvments -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10984) Remove IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option
Sergey Antonov created IGNITE-10984: --- Summary: Remove IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option Key: IGNITE-10984 URL: https://issues.apache.org/jira/browse/IGNITE-10984 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 3.0 We should rework logic and remove IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10979) Add documentation for control.sh idle_verify --check-crc
Sergey Antonov created IGNITE-10979: --- Summary: Add documentation for control.sh idle_verify --check-crc Key: IGNITE-10979 URL: https://issues.apache.org/jira/browse/IGNITE-10979 Project: Ignite Issue Type: New Feature Components: documentation Reporter: Sergey Antonov Assignee: Artem Budnikov Fix For: 2.8 We should document new option --check-crc in control.sh idle_verify command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10932) Remove inheritance between VisorIdleVerifyTaskArg and VisorIdleVerifyDumpTaskArg
Sergey Antonov created IGNITE-10932: --- Summary: Remove inheritance between VisorIdleVerifyTaskArg and VisorIdleVerifyDumpTaskArg Key: IGNITE-10932 URL: https://issues.apache.org/jira/browse/IGNITE-10932 Project: Ignite Issue Type: Improvement Affects Versions: 2.8 Reporter: Sergey Antonov Fix For: 3.0 VisorIdleVerifyDumpTaskArg shouldn't depends from VisorIdleVerifyTaskArg, because of it makes class extension difficult. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10826) Control.sh add logging to file
Sergey Antonov created IGNITE-10826: --- Summary: Control.sh add logging to file Key: IGNITE-10826 URL: https://issues.apache.org/jira/browse/IGNITE-10826 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10801) Update H2 verstion to 1.4.198
Sergey Antonov created IGNITE-10801: --- Summary: Update H2 verstion to 1.4.198 Key: IGNITE-10801 URL: https://issues.apache.org/jira/browse/IGNITE-10801 Project: Ignite Issue Type: Improvement Components: sql Affects Versions: 2.7 Reporter: Sergey Antonov Fix For: 2.8 After h2 1.4.198 release we should update h2 version in AI, because of important bugs will be fixed there. For example https://github.com/h2database/h2database/issues/1057 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10790) Control.sh add ability to check tx on deadlock
Sergey Antonov created IGNITE-10790:
---
Summary: Control.sh add ability to check tx on deadlock
Key: IGNITE-10790
URL: https://issues.apache.org/jira/browse/IGNITE-10790
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Fix For: 2.8
We should have ability to check selected transaction on deadlock in this moment.
Possible command: {{control.sh --tx detect_deadlock [,xid1,xid2]}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10789) CacheInterceptor on server node get BinaryObject if put was invoked by ClientCache.
Sergey Antonov created IGNITE-10789:
---
Summary: CacheInterceptor on server node get BinaryObject if put
was invoked by ClientCache.
Key: IGNITE-10789
URL: https://issues.apache.org/jira/browse/IGNITE-10789
Project: Ignite
Issue Type: Bug
Components: cache
Affects Versions: 2.7
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
Cache interceptor on server node expects deserialized object, but gets
BinaryObject in case of put was from thin client.
The exception is following:
{noformat}
[2018-12-21
17:25:08,213][ERROR][client-connector-#53%cache.Test20%][ClientListenerNioListener]
Failed to process client request
[req=o.a.i.i.processors.platform.client.cache.ClientCachePutRequest@72009659]
org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
(retry update if possible).: [key]
at
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1313)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1754)
at
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1107)
at
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:820)
at
org.apache.ignite.internal.processors.platform.client.cache.ClientCachePutRequest.process(ClientCachePutRequest.java:40)
at
org.apache.ignite.internal.processors.platform.client.ClientRequestHandler.handle(ClientRequestHandler.java:52)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:174)
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)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: class
org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
Failed to update keys (retry update if possible).: [key]
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:397)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onPrimaryResponse(GridNearAtomicSingleUpdateFuture.java:252)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:304)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture$1.apply(GridNearAtomicAbstractUpdateFuture.java:301)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicAbstractUpdateFuture.map(GridDhtAtomicAbstractUpdateFuture.java:394)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1942)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1671)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:300)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:482)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:442)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:249)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1153)
at
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:613)
[jira] [Created] (IGNITE-10780) control.sh add ability to get tx state change history
Sergey Antonov created IGNITE-10780: --- Summary: control.sh add ability to get tx state change history Key: IGNITE-10780 URL: https://issues.apache.org/jira/browse/IGNITE-10780 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 2.8 We should have ability to get info about tx state change history. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10761) GridCacheProcessor should add info about cache in excecption message, if applicable.
Sergey Antonov created IGNITE-10761: --- Summary: GridCacheProcessor should add info about cache in excecption message, if applicable. Key: IGNITE-10761 URL: https://issues.apache.org/jira/browse/IGNITE-10761 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov We should add info about problem cache in exception message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10742) Replace java.io.Console to GridConsole
Sergey Antonov created IGNITE-10742: --- Summary: Replace java.io.Console to GridConsole Key: IGNITE-10742 URL: https://issues.apache.org/jira/browse/IGNITE-10742 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 We should create and use GridConsole instead of java.io.Console because of using Console in tests impossible. The API of GridConsole must be identical Console API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10740) Add documentation for IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
Sergey Antonov created IGNITE-10740:
---
Summary: Add documentation for
IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT
Key: IGNITE-10740
URL: https://issues.apache.org/jira/browse/IGNITE-10740
Project: Ignite
Issue Type: Task
Components: documentation
Reporter: Sergey Antonov
Assignee: Artem Budnikov
Fix For: 2.8
We should add to documentation
IGNITE_DISABLE_TRIGGERING_CACHE_INTERCEPTOR_ON_CONFLICT option.
As a reference you could get javadoc from skipInterceptor() :
{{Checks, that cache interceptor should be skipped. It is expects by default
behavior that Interceptor methods (\{@link
CacheInterceptor#onBeforePut(Cache.Entry, Object)}, \{@link
CacheInterceptor#onAfterPut(Cache.Entry)}, \{@link
CacheInterceptor#onBeforeRemove(Cache.Entry)} and \{@link
CacheInterceptor#onAfterRemove(Cache.Entry)}) will be called, but \{@link
CacheInterceptor#onGet(Object, Object)}. This can even make DR-update flow
broken in case of non-idempotent Interceptor and force users to call onGet
manually as the only workaround. Also, user may want to skip Interceptor to
avoid redundant entry transformation for DR updates and exchange with internal
data b/w data centres which is a normal case.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10712) Control.sh add ability to get cluster metrics
Sergey Antonov created IGNITE-10712: --- Summary: Control.sh add ability to get cluster metrics Key: IGNITE-10712 URL: https://issues.apache.org/jira/browse/IGNITE-10712 Project: Ignite Issue Type: New Feature Reporter: Sergey Antonov Fix For: 3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10699) Update documentation for control.sh
Sergey Antonov created IGNITE-10699:
---
Summary: Update documentation for control.sh
Key: IGNITE-10699
URL: https://issues.apache.org/jira/browse/IGNITE-10699
Project: Ignite
Issue Type: Task
Affects Versions: 2.8
Reporter: Sergey Antonov
Assignee: Artem Budnikov
I renamed view parameters in control.sh utility. The changes are following:
||Was||Has been||
|--skipZeros|--skip-zeros|
|--cacheFilter|--cache-filter|
|checkFirst|--check-first|
|checkThrough|--check-through|
|limit| --limit|
|order|--order|
|minDuration|--min-duration|
|minSize|--min-size|
|label|--label|
|nodes|--nodes|
|xid|--xid|
You could find current output command {{control.sh --cache help}}
{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov
The '--cache subcommand' is used to get information about and perform actions
with caches. The command has the following syntax:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
[--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ...]] [--ssl-cipher-suites
SSL_CIPHER_1[, SSL_CIPHER_2, ...]] [--ssl-key-algorithm SSL_KEY_ALGORITHM]
[--keystore-type KEYSTORE_TYPE] [--keystore KEYSTORE] [--keystore-password
KEYSTORE_PASSWORD] [--truststore-type TRUSTSTORE_TYPE] [--truststore
TRUSTSTORE] [--truststore-password TRUSTSTORE_PASSWORD] --cache[subcommand]
The subcommands that take [nodeId] as an argument ('list', 'contention' and
'validate_indexes') will be executed on the given node or on all server nodes
if the option is not specified. Other commands will run on a random server node.
Subcommands:
--cache list regexPattern [groups|seq] [nodeId] [--config] [--output-format
multi-line]
Show information about caches, groups or sequences that match a regular
expression. When executed without parameters, this subcommand prints the list
of caches.
Parameters:
--config - print a all configuration parameters for each cache.
--output-format multi-line - print configuration parameters per line. This
option has effect only when used with --config and without [groups|seq].
--cache contention minQueueSize [nodeId] [maxPrint]
Show the keys that are point of contention for multiple transactions.
--cache idle_verify [--dump] [--skip-zeros] [cache1,...,cacheN] [--cache-filter
ALL|SYSTEM|PERSISTENT|NOT_PERSISTENT]
Verify counters and hash sums of primary and backup partitions for the
specified caches on an idle cluster and print out the differences, if any.
--cache validate_indexes [cache1,...,cacheN] [nodeId] [--check-first
N|--check-through K]
Validate indexes on an idle cluster and print out the keys that are missing in
the indexes.
Parameters:
--check-first N - validate only the first N keys
--check-through K - validate every Kth key
--cache distribution nodeId|null [cacheName1,...,cacheNameN] [--user-attributes
attName1,...,attrNameN]
Prints the information about partition distribution.
--cache reset_lost_partitions cacheName1,...,cacheNameN
Reset the state of lost partitions for the specified caches.{noformat}
And {{control.sh --help}}
{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov
Contol.sh is used to execute admin commands on cluster or get common cluster
info. The command has the following syntax:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
[--ssl-protocol SSL_PROTOCOL[, SSL_PROTOCOL_2, ...]] [--ssl-cipher-suites
SSL_CIPHER_1[, SSL_CIPHER_2, ...]] [--ssl-key-algorithm SSL_KEY_ALGORITHM]
[--keystore-type KEYSTORE_TYPE] [--keystore KEYSTORE] [--keystore-password
KEYSTORE_PASSWORD] [--truststore-type TRUSTSTORE_TYPE] [--truststore
TRUSTSTORE] [--truststore-password TRUSTSTORE_PASSWORD] [command]
This utility can do the following commands:
Activate cluster:
control.sh --activate
Deactivate cluster:
control.sh --deactivate [--yes]
Print current cluster state:
control.sh --state
Print cluster baseline topology:
control.sh
[jira] [Created] (IGNITE-10649) Add documentation for control.sh about SSL
Sergey Antonov created IGNITE-10649: --- Summary: Add documentation for control.sh about SSL Key: IGNITE-10649 URL: https://issues.apache.org/jira/browse/IGNITE-10649 Project: Ignite Issue Type: Task Components: documentation Reporter: Sergey Antonov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10507) VisorIdleVerifyTask should return exceptions from all nodes if they are occured
Sergey Antonov created IGNITE-10507: --- Summary: VisorIdleVerifyTask should return exceptions from all nodes if they are occured Key: IGNITE-10507 URL: https://issues.apache.org/jira/browse/IGNITE-10507 Project: Ignite Issue Type: Improvement Components: visor Affects Versions: 2.6 Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 We should return exceptions from all nodes, if they are occured. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10427) GridClusterStateProcessor#changeGlobalState0() should wrap future before sending ChangeGlobalStateMessage
Sergey Antonov created IGNITE-10427: --- Summary: GridClusterStateProcessor#changeGlobalState0() should wrap future before sending ChangeGlobalStateMessage Key: IGNITE-10427 URL: https://issues.apache.org/jira/browse/IGNITE-10427 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10399) Fix inspection failures
Sergey Antonov created IGNITE-10399: --- Summary: Fix inspection failures Key: IGNITE-10399 URL: https://issues.apache.org/jira/browse/IGNITE-10399 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov 1 error in master branch https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_InspectionsCore_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10384) Stop caches in parallel
Sergey Antonov created IGNITE-10384: --- Summary: Stop caches in parallel Key: IGNITE-10384 URL: https://issues.apache.org/jira/browse/IGNITE-10384 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 Stopping 6000+ caches sequentially go on more 80 seconds. We must parallel this process. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10281) Log to file all jars in classpath on start node.
Sergey Antonov created IGNITE-10281: --- Summary: Log to file all jars in classpath on start node. Key: IGNITE-10281 URL: https://issues.apache.org/jira/browse/IGNITE-10281 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 2.8 We should print all jars in classpath for analize jar's hell. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10279) Control.sh utility unify options naming format
Sergey Antonov created IGNITE-10279: --- Summary: Control.sh utility unify options naming format Key: IGNITE-10279 URL: https://issues.apache.org/jira/browse/IGNITE-10279 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 Now we have options in several styles: --ping-interval, --skipZeros. I think, we must unify options naming format. We should follow linux format, i.e. --word1-word2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10258) control.sh: make optional parameters order irrelevant
Sergey Antonov created IGNITE-10258:
---
Summary: control.sh: make optional parameters order irrelevant
Key: IGNITE-10258
URL: https://issues.apache.org/jira/browse/IGNITE-10258
Project: Ignite
Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov
Fix For: 2.8
{noformat}
IGNITE_HOME=`pwd` bin/control.sh --cache idle_verify --host 172.25.1.14 --dump
Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7]
2018 Copyright(C) Apache Software Foundation
User: mshonichev
Check arguments.
Error: Unexpected argument: --dump{noformat}
{noformat}
IGNITE_HOME=`pwd` bin/control.sh --host 172.25.1.14 --cache idle_verify --dump
Control utility [ver. 2.5.1-p160#20181113-sha1:5f845ca7] 2018 Copyright(C)
Apache Software Foundation User: mshonichev
VisorIdleVerifyDumpTask successfully written output to
'/storage/ssd/mshonichev/tiden/pme-181114-163416/test_pme_bench/ignite.server.1/work/idle-dump-2018-11-14T16-46-34_246.txt'
{noformat}
It is quite unexpected and unpleasant that re-ordering optional arguments to
the --cache idle_verify command makes it throw error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10257) Control.sh utility should request a SSL keystore password and SSL truststore password if necessary
Sergey Antonov created IGNITE-10257: --- Summary: Control.sh utility should request a SSL keystore password and SSL truststore password if necessary Key: IGNITE-10257 URL: https://issues.apache.org/jira/browse/IGNITE-10257 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10233) GridAffinityAssignmentCache#cachedAffinity() should not check topology version in assertion, if cluster not activated.
Sergey Antonov created IGNITE-10233: --- Summary: GridAffinityAssignmentCache#cachedAffinity() should not check topology version in assertion, if cluster not activated. Key: IGNITE-10233 URL: https://issues.apache.org/jira/browse/IGNITE-10233 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov It's needed for our proprietary plugin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10218) Detecting lost partitions PME phase triggered twice on coordinator
Sergey Antonov created IGNITE-10218:
---
Summary: Detecting lost partitions PME phase triggered twice on
coordinator
Key: IGNITE-10218
URL: https://issues.apache.org/jira/browse/IGNITE-10218
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Fix For: 2.8
scenarion: 1 server left
coordinator node seems to detect partition losses twice per exchange
{noformat}
[16:54:22,027][INFO][exchange-worker-#66][time] Finished exchange init
[topVer=AffinityTopologyVersion [topVer=13, minorTopVer=0], crd=true]
[16:54:22,163][INFO][db-checkpoint-thread-#86][GridCacheDatabaseSharedManager]
Skipping checkpoint (no pages were modified) [checkpointLockWait=0ms,
checkpointLockHoldTime=525ms, reason='timeout']
[16:54:22,338][INFO][sys-#136][GridDhtPartitionsExchangeFuture] Coordinator
received single message [ver=AffinityTopologyVersion [topVer=13,
minorTopVer=0], node=2b69b32f-1bea-4c83-a70d-d7ff8ad7e319, allReceived=false]
[16:54:22,401][INFO][sys-#137][GridDhtPartitionsExchangeFuture] Coordinator
received single message [ver=AffinityTopologyVersion [topVer=13,
minorTopVer=0], node=933628df-5237-435c-81d3-7d4be20d8cea, allReceived=false]
[16:54:22,405][INFO][sys-#73][GridDhtPartitionsExchangeFuture] Coordinator
received single message [ver=AffinityTopologyVersion [topVer=13,
minorTopVer=0], node=549935a6-48b0-47cd-a763-13cef4706960, allReceived=false]
[16:54:22,413][INFO][sys-#121][GridDhtPartitionsExchangeFuture] Coordinator
received single message [ver=AffinityTopologyVersion [topVer=13,
minorTopVer=0], node=fbdde4e1-2422-49af-a0bb-d6797cc723fe, allReceived=false]
[16:54:22,722][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Coordinator
received single message [ver=AffinityTopologyVersion [topVer=13,
minorTopVer=0], node=d67a748d-9c63-4ede-8dae-064b63dd1586, allReceived=true]
[16:54:23,493][INFO][db-checkpoint-thread-#86][GridCacheDatabaseSharedManager]
Skipping checkpoint (no pages were modified) [checkpointLockWait=0ms,
checkpointLockHoldTime=849ms, reason='timeout']
[16:54:23,494][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Coordinator
received all messages, try merge [ver=AffinityTopologyVersion [topVer=13,
minorTopVer=0]]
[16:54:23,494][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Exchanges
merging performed in 0 ms.
[16:54:23,494][INFO][sys-#122][GridDhtPartitionsExchangeFuture]
finishExchangeOnCoordinator [topVer=AffinityTopologyVersion [topVer=13,
minorTopVer=0], resVer=AffinityTopologyVersion [topVer=13, minorTopVer=0]]
[16:54:24,223][INFO][sys-#122][CacheAffinitySharedManager] Affinity
recalculation (on server left) performed in 729 ms.
[16:54:24,371][INFO][db-checkpoint-thread-#86][GridCacheDatabaseSharedManager]
Skipping checkpoint (no pages were modified) [checkpointLockWait=0ms,
checkpointLockHoldTime=726ms, reason='timeout']
[16:54:25,146][INFO][db-checkpoint-thread-#86][GridCacheDatabaseSharedManager]
Skipping checkpoint (no pages were modified) [checkpointLockWait=1ms,
checkpointLockHoldTime=493ms, reason='timeout']
[16:54:26,443][INFO][db-checkpoint-thread-#86][GridCacheDatabaseSharedManager]
Skipping checkpoint (no pages were modified) [checkpointLockWait=8ms,
checkpointLockHoldTime=776ms, reason='timeout']
[16:54:26,443][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Affinity
changes (coordinator) applied in 2949 ms.
[16:54:26,758][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Partitions
validation performed in 307 ms.
[16:54:27,398][INFO][db-checkpoint-thread-#86][GridCacheDatabaseSharedManager]
Skipping checkpoint (no pages were modified) [checkpointLockWait=0ms,
checkpointLockHoldTime=725ms, reason='timeout']
[16:54:27,646][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Detecting lost
partitions performed in 887 ms.
[16:54:28,908][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Preparing Full
Message performed in 1138 ms.
[16:54:28,908][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full
Message performed in 0 ms.
[16:54:28,908][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Sending Full
Message to all nodes performed in 0 ms.
[16:54:28,908][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Finish exchange
future [startVer=AffinityTopologyVersion [topVer=13, minorTopVer=0],
resVer=AffinityTopologyVersion [topVer=13, minorTopVer=0], err=null]
[16:54:29,171][INFO][db-checkpoint-thread-#86][GridCacheDatabaseSharedManager]
Skipping checkpoint (no pages were modified) [checkpointLockWait=0ms,
checkpointLockHoldTime=486ms, reason='timeout']
[16:54:29,316][INFO][sys-#122][GridDhtPartitionsExchangeFuture] Detecting lost
partitions performed in 407 ms.
{noformat}
This method is invoked two times:
# GridDhtPartitionsExchangeFuture#finishExchangeOnCoordinator()
# GridDhtPartitionsExchangeFuture#onDone()
Do we really need to perform Detecting lost partitions twice?
--
This message was sent by
[jira] [Created] (IGNITE-10212) Add information about topology version in all messages related with PME
Sergey Antonov created IGNITE-10212: --- Summary: Add information about topology version in all messages related with PME Key: IGNITE-10212 URL: https://issues.apache.org/jira/browse/IGNITE-10212 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Fix For: 2.8 We need to see topology version in all messages related with partitions map exchange. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10130) Add option to API for disable triggering cache interceptor.
Sergey Antonov created IGNITE-10130: --- Summary: Add option to API for disable triggering cache interceptor. Key: IGNITE-10130 URL: https://issues.apache.org/jira/browse/IGNITE-10130 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10113) Failure during build index isn't handled by failure handler
Sergey Antonov created IGNITE-10113: --- Summary: Failure during build index isn't handled by failure handler Key: IGNITE-10113 URL: https://issues.apache.org/jira/browse/IGNITE-10113 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov Fix For: 2.8 Attachments: StopNodeOnRebuildIndexFailureTest.java If exception will be thrown during index build, failure handler doesn't handle this exception. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9963) Tests with mvn command invocation failed if path to M2_HOME contains spaces.
Sergey Antonov created IGNITE-9963:
--
Summary: Tests with mvn command invocation failed if path to
M2_HOME contains spaces.
Key: IGNITE-9963
URL: https://issues.apache.org/jira/browse/IGNITE-9963
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Assignee: Sergey Antonov
If path to M2_HOME contains spaces, tests with mvn invocation are failed with
following exception:
{noformat}
Command='C:\Program Files\apache-maven-3.5.4/bin/mvn help:effective-settings'
couldn't be executed: 'C:\Program' is not recognized as an internal or external
command, operable program or batch file. UTF-8 java.lang.Exception: Abnormal
exit value of 1 for pid 4652 [2018-10-22 14:49:28,032][INFO ][main][root] >>>
Stopping test:
PersistenceBasicCompatibilityTest#testNodeStartByOldVersionPersistenceData_2_1
in 968 ms <<< [2018-10-22 14:49:28,028][ERROR][main][root] Test failed.
java.lang.Exception: Abnormal exit value of 1 for pid 4652 at
org.apache.ignite.compatibility.testframework.util.MavenUtils.exec(MavenUtils.java:191)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.defineMavenLocalRepositoryPath(MavenUtils.java:132)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.getMavenLocalRepositoryPath(MavenUtils.java:120)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.getPathToArtifact(MavenUtils.java:101)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.getPathToIgniteArtifact(MavenUtils.java:70)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest$1.filteredJvmArgs(IgniteCompatibilityAbstractTest.java:186)
at
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy.(IgniteProcessProxy.java:173)
at
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy.(IgniteProcessProxy.java:148)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest$1.(IgniteCompatibilityAbstractTest.java:143)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest.startGrid(IgniteCompatibilityAbstractTest.java:143)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest.startGrid(IgniteCompatibilityAbstractTest.java:116)
at
org.apache.ignite.compatibility.persistence.PersistenceBasicCompatibilityTest.doTestStartupWithOldVersion(PersistenceBasicCompatibilityTest.java:113)
at
org.apache.ignite.compatibility.persistence.PersistenceBasicCompatibilityTest.doTestStartupWithOldVersion(PersistenceBasicCompatibilityTest.java:139)
at
org.apache.ignite.compatibility.persistence.PersistenceBasicCompatibilityTest.testNodeStartByOldVersionPersistenceData_2_1(PersistenceBasicCompatibilityTest.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498) at
junit.framework.TestCase.runTest(TestCase.java:176) at
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2176)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:142)
at
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2091)
at java.lang.Thread.run(Thread.java:748) java.lang.Exception: Abnormal exit
value of 1 for pid 4652 at
org.apache.ignite.compatibility.testframework.util.MavenUtils.exec(MavenUtils.java:191)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.defineMavenLocalRepositoryPath(MavenUtils.java:132)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.getMavenLocalRepositoryPath(MavenUtils.java:120)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.getPathToArtifact(MavenUtils.java:101)
at
org.apache.ignite.compatibility.testframework.util.MavenUtils.getPathToIgniteArtifact(MavenUtils.java:70)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest$1.filteredJvmArgs(IgniteCompatibilityAbstractTest.java:186)
at
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy.(IgniteProcessProxy.java:173)
at
org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy.(IgniteProcessProxy.java:148)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest$1.(IgniteCompatibilityAbstractTest.java:143)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest.startGrid(IgniteCompatibilityAbstractTest.java:143)
at
org.apache.ignite.compatibility.testframework.junits.IgniteCompatibilityAbstractTest.startGrid(IgniteCompatibilityAbstractTest.java:116)
at
[jira] [Created] (IGNITE-9931) Fix flaky failures in IgniteTopologyValidatorGridSplitCacheTest
Sergey Antonov created IGNITE-9931: -- Summary: Fix flaky failures in IgniteTopologyValidatorGridSplitCacheTest Key: IGNITE-9931 URL: https://issues.apache.org/jira/browse/IGNITE-9931 Project: Ignite Issue Type: Test Reporter: Sergey Antonov Assignee: Sergey Antonov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9868) Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating
Sergey Antonov created IGNITE-9868: -- Summary: Refactor [GridCachePartitionExchangeManager] Sending Full Message/Full Message creating Key: IGNITE-9868 URL: https://issues.apache.org/jira/browse/IGNITE-9868 Project: Ignite Issue Type: Improvement Reporter: Sergey Antonov Assignee: Sergey Antonov Made messages more informative and, maybe, reduce number of messages in log file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9856) Add documentation for control.sh --cache config
Sergey Antonov created IGNITE-9856:
--
Summary: Add documentation for control.sh --cache config
Key: IGNITE-9856
URL: https://issues.apache.org/jira/browse/IGNITE-9856
Project: Ignite
Issue Type: Improvement
Components: documentation
Reporter: Sergey Antonov
Option {{--cache config}} in {{control.sh}} must be documented.
As reference could be used help message:
{noformat}
List caches configuration:
control.sh [--host HOST_OR_IP] [--port PORT] [--user USER] [--password
PASSWORD] [--ping-interval PING_INTERVAL] [--ping-timeout PING_TIMEOUT]
--cache config cacheNameRegexPattern [--human-readable]
{noformat}
And output example:
{noformat}
Control utility [ver. 2.7.0-SNAPSHOT#19700101-sha1:DEV]
2018 Copyright(C) Apache Software Foundation
User: santonov
ignite-sys-cache: {Name=ignite-sys-cache, Group=null, Dynamic Deployment
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=true,
Mode=REPLICATED, Atomicity Mode=TRANSACTIONAL, Statistic Enabled=false,
Management Enabled=false, On-heap cache enabled=false, Partition Loss
Policy=IGNORE, Query Parallelism=1, Copy On Read=false, Listener
Configurations=null, Load Previous Value=false, Memory Policy Name=sysMemPlc,
Node Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate,
Read From Backup=true, Topology Validator=null, Time To Live Eager Flag=true,
Write Synchronization Mode=FULL_SYNC, Invalidate=false, Affinity
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
Backups=2147483647, Affinity Partitions=100, Affinity Exclude Neighbors=false,
Affinity Mapper=o.a.i.i.processors.cache.GridCacheDefaultAffinityKeyMapper,
Rebalance Mode=SYNC, Rebalance Batch Size=524288, Rebalance Timeout=1,
Rebalance Delay=0, Time Between Rebalance Messages=0, Rebalance Batches
Count=2, Rebalance Cache Order=-2, Eviction Policy Enabled=false, Eviction
Policy Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near
Cache Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false,
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class
Name=null, Expiry Policy Factory Class
Name=javax.cache.configuration.FactoryBuilder$SingletonFactory, Query Execution
Time Threshold=3000, Query Escaped Names=false, Query SQL Schema=null, Query
SQL functions=null, Query Indexed Types=null, Maximum payload size for offheap
indexes=-1, Query Metrics History Size=0}
test-default: {Name=test-default, Group=null, Dynamic Deployment
ID=fb381836661-93ea1b62-7e2c-449d-82f4-ede849a03e22, System=false,
Mode=PARTITIONED, Atomicity Mode=ATOMIC, Statistic Enabled=false, Management
Enabled=false, On-heap cache enabled=false, Partition Loss Policy=IGNORE, Query
Parallelism=1, Copy On Read=true, Listener Configurations=null, Load Previous
Value=false, Memory Policy Name=null, Node
Filter=o.a.i.configuration.CacheConfiguration$IgniteAllNodesPredicate, Read
From Backup=true, Topology Validator=null, Time To Live Eager Flag=true, Write
Synchronization Mode=PRIMARY_SYNC, Invalidate=false, Affinity
Function=o.a.i.cache.affinity.rendezvous.RendezvousAffinityFunction, Affinity
Backups=0, Affinity Partitions=1024, Affinity Exclude Neighbors=false, Affinity
Mapper=o.a.i.i.processors.cache.CacheDefaultBinaryAffinityKeyMapper, Rebalance
Mode=ASYNC, Rebalance Batch Size=524288, Rebalance Timeout=1, Rebalance
Delay=0, Time Between Rebalance Messages=0, Rebalance Batches Count=2,
Rebalance Cache Order=0, Eviction Policy Enabled=false, Eviction Policy
Factory=null, Eviction Policy Max Size=null, Eviction Filter=null, Near Cache
Enabled=false, Near Start Size=0, Near Eviction Policy Factory=null, Near
Eviction Policy Max Size=null, Default Lock Timeout=0, Query Entities=[], Cache
Interceptor=null, Store Enabled=false, Store Class=null, Store Factory
Class=null, Store Keep Binary=false, Store Read Through=false, Store Write
Through=false, Store Write Coalescing=true, Write-Behind Enabled=false,
Write-Behind Flush Size=10240, Write-Behind Frequency=5000, Write-Behind Flush
Threads Count=1, Write-Behind Batch Size=512, Concurrent Asynchronous
Operations Number=500, Loader Factory Class Name=null, Writer Factory Class
Name=null, Expiry Policy Factory Class
Name=javax.cache.configuration.FactoryBuilder$SingletonFactory, Query
[jira] [Created] (IGNITE-9853) control.sh show more information about cache configuration
Sergey Antonov created IGNITE-9853: -- Summary: control.sh show more information about cache configuration Key: IGNITE-9853 URL: https://issues.apache.org/jira/browse/IGNITE-9853 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov Assignee: Sergey Antonov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9743) Fix broken link to DML example on https://ignite.apache.org/features/sql.html
Sergey Antonov created IGNITE-9743: -- Summary: Fix broken link to DML example on https://ignite.apache.org/features/sql.html Key: IGNITE-9743 URL: https://issues.apache.org/jira/browse/IGNITE-9743 Project: Ignite Issue Type: Bug Reporter: Sergey Antonov On page [https://ignite.apache.org/features/sql.html] in section *GitHub examples* *DML example* linking with non existing page. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9674) Double p2p class loading
Sergey Antonov created IGNITE-9674:
--
Summary: Double p2p class loading
Key: IGNITE-9674
URL: https://issues.apache.org/jira/browse/IGNITE-9674
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
Attachments: AlwaysTrueTestPredicate.java,
DoubleP2PClassLoadingTest.java, always-true-predicate.jar
On p2p class loading {{GridDeploymentRequest}} will be sent twice:
First time it will be in {{GridDeploymentPerVersionStore}}#checkLoadRemoteClass
line 715
Second time it will be in {{GridDeploymentPerVersionStore#getDeployment line
500}}
*How to reproduce:*
# Remove {{AlwaysTrueTestPredicate}} from CLASSPATH, for example, pack to jar
file.
# Run {{DoubleP2PClassLoadingTest}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9466) AsyncFileIO may not close channel after method close invocation
Sergey Antonov created IGNITE-9466:
--
Summary: AsyncFileIO may not close channel after method close
invocation
Key: IGNITE-9466
URL: https://issues.apache.org/jira/browse/IGNITE-9466
Project: Ignite
Issue Type: Bug
Reporter: Sergey Antonov
{code:java}
/** {@inheritDoc} */
@Override public void close() throws IOException {
for (ChannelOpFuture asyncFut : asyncFuts) {
try {
asyncFut.getUninterruptibly(); // Ignore interrupts while waiting
for channel close.
}
catch (IgniteCheckedException e) {
throw new IOException(e);
}
}
ch.close();
}{code}
If `asyncFut.getUninterruptibly()` throw exception, the channel associated with
AsyncFileIO will not be closed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9438) StandaloneWalRecordsIterator file descriptors leak
Sergey Antonov created IGNITE-9438:
--
Summary: StandaloneWalRecordsIterator file descriptors leak
Key: IGNITE-9438
URL: https://issues.apache.org/jira/browse/IGNITE-9438
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Sergey Antonov
Fix For: 2.7
In {{StandaloneWalRecordsIterator#initReadHandle()}} method are opens file
descriptor.
{code:java}
FileIO fileIO = fd.isCompressed() ? new UnzipFileIO(fd.file()) :
ioFactory.create(fd.file());
{code}
It not used after attempt to read segment header and it don't closed.
Second time same file descriptor are opens in super method
{{AbstractWalRecordsIterator#initReadHandle()}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
