[jira] [Created] (IGNITE-13540) Exchange worker, waiting for new task from queue, considered as blocked.
Ivan Daschinskiy created IGNITE-13540:
-
Summary: Exchange worker, waiting for new task from queue,
considered as blocked.
Key: IGNITE-13540
URL: https://issues.apache.org/jira/browse/IGNITE-13540
Project: Ignite
Issue Type: Bug
Reporter: Ivan Daschinskiy
Assignee: Ivan Daschinskiy
Waiting for new task in ExchangeWorker#body now is not marking as blocking
section.
So if network timeout (timeout for polling task from queue) is greater than
system worker blocked timeout, exchange worker thread is considered as
blocking. Sometimes this is reported in logs after few seconds when actually
PME is finished
{noformat}
[2020-10-06 16:55:45,939][INFO
][exchange-worker-#50][org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager1]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=6, minorTopVer=1], force=false, evt=DISCOVERY_CUSTOM_EVT,
node=163fd0f0-b9a4-4317-a28f-f7dbdb776076]
[2020-10-06 16:55:48,822][ERROR][tcp-disco-msg-worker-[9e18957a
172.18.0.5:47500]-#2-#44][org.apache.ignite.internal.util.typedef.G1] Blocked
system-critical thread has been detected. This can lead to cluster-wide
undefined behaviour [workerName=partition-exchanger,
threadName=exchange-worker-#50, blockedFor=2s]
[2020-10-06 16:55:48,824][WARN ][tcp-disco-msg-worker-[9e18957a
172.18.0.5:47500]-#2-#44][org.apache.ignite.internal.util.typedef.G1] Thread
[name="exchange-worker-#50", id=90, state=TIMED_WAITING, blockCnt=20,
waitCnt=48]
Lock
[object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@14f29e0e,
ownerName=null, ownerId=-1]
[2020-10-06 16:55:48,827][WARN ][tcp-disco-msg-worker-[9e18957a
172.18.0.5:47500]-#2-#44][root1] Possible failure suppressed accordingly to a
configured handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class
o.a.i.IgniteException: GridWorker [name=partition-exchanger,
igniteInstanceName=null, finished=false, heartbeatTs=1601992545941]]]
class org.apache.ignite.IgniteException: GridWorker [name=partition-exchanger,
igniteInstanceName=null, finished=false, heartbeatTs=1601992545941]
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$3.apply(IgnitionEx.java:1860)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$3.apply(IgnitionEx.java:1855)
at
org.apache.ignite.internal.worker.WorkersRegistry.onIdle(WorkersRegistry.java:234)
at
org.apache.ignite.internal.util.worker.GridWorker.onIdle(GridWorker.java:299)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13541) Calcite integration. Support of Date/Time types
Yury Gerzhedovich created IGNITE-13541: -- Summary: Calcite integration. Support of Date/Time types Key: IGNITE-13541 URL: https://issues.apache.org/jira/browse/IGNITE-13541 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich Seems currently the new Calcite engine doesn't support date/time types. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13542) Calcite integration. Type system
Yury Gerzhedovich created IGNITE-13542: -- Summary: Calcite integration. Type system Key: IGNITE-13542 URL: https://issues.apache.org/jira/browse/IGNITE-13542 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich System of types for the new Calcite engine . Just review, seems it may be used as-is + write many tests. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13543) Calcite integration. Support of merge aggregates
Yury Gerzhedovich created IGNITE-13543: -- Summary: Calcite integration. Support of merge aggregates Key: IGNITE-13543 URL: https://issues.apache.org/jira/browse/IGNITE-13543 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich To have a performance boost need to implement merge aggregates. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13544) Calcite integration.
Yury Gerzhedovich created IGNITE-13544: -- Summary: Calcite integration. Key: IGNITE-13544 URL: https://issues.apache.org/jira/browse/IGNITE-13544 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich To have a performance boost need to implement merge joins. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13545) Calcite integration. Index spoon
Yury Gerzhedovich created IGNITE-13545: -- Summary: Calcite integration. Index spoon Key: IGNITE-13545 URL: https://issues.apache.org/jira/browse/IGNITE-13545 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich To have a performance boost need to implement index spoons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13546) Calcite integration. Hash index spoon
Yury Gerzhedovich created IGNITE-13546: -- Summary: Calcite integration. Hash index spoon Key: IGNITE-13546 URL: https://issues.apache.org/jira/browse/IGNITE-13546 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich To have a performance boost need to implement hash index spoons. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13547) Calcite integration. CREATE TABLE support
Yury Gerzhedovich created IGNITE-13547: -- Summary: Calcite integration. CREATE TABLE support Key: IGNITE-13547 URL: https://issues.apache.org/jira/browse/IGNITE-13547 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich We need to support DDL commands. The task about the support of CREATE TABLE. Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13548) Calcite integration. DROP TABLE support
Yury Gerzhedovich created IGNITE-13548: -- Summary: Calcite integration. DROP TABLE support Key: IGNITE-13548 URL: https://issues.apache.org/jira/browse/IGNITE-13548 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich We need to support DDL commands. The task about the support of DROP TABLE. Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13549) Calcite integration. CREATE/DROP INDEX support
Yury Gerzhedovich created IGNITE-13549: -- Summary: Calcite integration. CREATE/DROP INDEX support Key: IGNITE-13549 URL: https://issues.apache.org/jira/browse/IGNITE-13549 Project: Ignite Issue Type: New Feature Components: sql Reporter: Yury Gerzhedovich We need to support DDL commands. The task about the support of CREATE/DROP INDEX. Potentially with syntaxis as we already have in the H2 engine. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13550) CLI command to execute maintenance action in corrupted PDS scenario
Sergey Chugunov created IGNITE-13550: Summary: CLI command to execute maintenance action in corrupted PDS scenario Key: IGNITE-13550 URL: https://issues.apache.org/jira/browse/IGNITE-13550 Project: Ignite Issue Type: Task Components: control.sh Reporter: Sergey Chugunov Assignee: Sergey Chugunov Fix For: 2.10 IGNITE-13366 introduces Maintenance Mode for corrupted PDS scenario and changes previous behavior of automatic deletion of corrupted PDS files. New command is needed so user is able to get information about maintenance task and trigger needed action. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13551) .NET: Enable ClientServerCompatibilityTest on Linux
Pavel Tupitsyn created IGNITE-13551: --- Summary: .NET: Enable ClientServerCompatibilityTest on Linux Key: IGNITE-13551 URL: https://issues.apache.org/jira/browse/IGNITE-13551 Project: Ignite Issue Type: Improvement Components: platforms Reporter: Pavel Tupitsyn Assignee: Pavel Tupitsyn Fix For: 2.10 ClientServerCompatibilityTest is disabled on Linux because it hangs. The problem is now understood: IGNITE-13536. Use the workaround - create processes from Java - and enable the test on all platforms and frameworks. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13552) PME-free test should check both drops (PME duration vs PME-free, Tx wait vs wait-free)
Anton Vinogradov created IGNITE-13552: - Summary: PME-free test should check both drops (PME duration vs PME-free, Tx wait vs wait-free) Key: IGNITE-13552 URL: https://issues.apache.org/jira/browse/IGNITE-13552 Project: Ignite Issue Type: Task Reporter: Anton Vinogradov Assignee: Anton Vinogradov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13553) Node failure with ClassNotFoundException when indexed field of QueryEntity differs from type used in put operation
Ilya Shishkov created IGNITE-13553:
--
Summary: Node failure with ClassNotFoundException when indexed
field of QueryEntity differs from type used in put operation
Key: IGNITE-13553
URL: https://issues.apache.org/jira/browse/IGNITE-13553
Project: Ignite
Issue Type: Bug
Components: sql, thin client
Affects Versions: 2.8.1, 2.9, 2.10
Reporter: Ilya Shishkov
Failures occur under these conditions:
# Data classes are not present in server classpaths, peer-classloading is not
used because thin client is used.
# Manual construction of QueryEntity via #setFields, #setIndexes etc. is used
instead of constructor of QueryEntity in conjunction with @QuerySqlField for
data clases.
# One of the indexed fields of QueryEntity has type different from type of
corresponding field of data object instance, eg:
{code:java|title=QueryEntity}
fields.put("name", "java.lang.String");
fields.put("wrongTypeEmbeddable", "java.lang.String"); /* This is wrong type */
QueryEntity qryEntity = new QueryEntity()
.setKeyType("java.lang.Integer")
.setValueType("org.apache.ignite.wrongtype.WrongTypeEntity") /* FQDN
should be used */
.setFields(fields)
.setIndexes(Collections.singleton(
new QueryIndex("wrongTypeEmbeddable") /* Wrong type field is
indexed */));
{code}
{code:java|title=Embedded field type in put operation is different}
cache.put(0, new WrongTypeEntity("name",
new WrongTypeEmbeddable(256, "testField") /* wrongTypeEmbeddable field
*/));
{code}
How to reproduce:
# Start server nodes with default condig via ignite.sh
# Run reproducer:
For Apache Ignite 2.8.1 failures are identical for atomic and transactional
caches:
{code:java}
[17:45:23,108][SEVERE][sys-stripe-0-#1][] JVM will be halted immediately due to
the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.binary.BinaryInvalidTypeException: o.a.i.wrongtype.WrongTypeEmbeddable]]
{code}
For AI, built and assemblied from master, failure is supressed for atomic and
occur only for transactional caches:
{code:java}
[17:39:09,305][SEVERE][sys-stripe-10-#11][] JVM will be halted immediately due
to the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class
o.a.i.i.transactions.IgniteTxHeuristicCheckedException: Committing a
transaction has produced runtime exception]]
{code}
Root cause for all failures is:
{code:java}
Caused by: java.lang.ClassNotFoundException:
org.apache.ignite.wrongtype.WrongTypeEmbeddable
{code}
Logs:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13554) ConcurrentModificationException on node join.
Stanilovsky Evgeny created IGNITE-13554:
---
Summary: ConcurrentModificationException on node join.
Key: IGNITE-13554
URL: https://issues.apache.org/jira/browse/IGNITE-13554
Project: Ignite
Issue Type: Bug
Components: general
Reporter: Stanilovsky Evgeny
{noformat}
java.util.ConcurrentModificationException: null
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1445)
at java.util.HashMap$EntryIterator.next(HashMap.java:1479)
at java.util.HashMap$EntryIterator.next(HashMap.java:1477)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.fillAffinityNodeCaches(GridDiscoveryManager.java:3278)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.createDiscoCache(GridDiscoveryManager.java:2364)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.access$3100(GridDiscoveryManager.java:171)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:723)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:528)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2608)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2646)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: Security issue with control.sh and ignite.sh
Hi Sam, Good catch! What exactly should user do to enable JMX? Should the user pass some additional arguments to scripts? It worth mentioning it in the ticket and later in documentation. 2020-10-06 13:50 GMT+03:00, Данилов Семён : > Hello, Igniters! > > I recently got my eye on the fact that we have JMX enabled by default and > it's configured in a very insecure way. > Our default JMX parameters are authenticate=false and ssl=false. > > I propose removing default configuration of JMX altogether, as user must > *consciously* and carefully configure such dangerous things. > > I created an issue (https://issues.apache.org/jira/browse/IGNITE-13478) and > pull request for those changes > (https://github.com/apache/ignite/pull/8304). > > Cheers, Sam. > -- Best regards, Ivan Pavlukhin
[jira] [Created] (IGNITE-13555) Java thin: Add support for IPv6 addresses
Pavel Tupitsyn created IGNITE-13555: --- Summary: Java thin: Add support for IPv6 addresses Key: IGNITE-13555 URL: https://issues.apache.org/jira/browse/IGNITE-13555 Project: Ignite Issue Type: Improvement Components: thin client Reporter: Pavel Tupitsyn Fix For: 2.10 ReliableChannel#parseAddresses -> HostAndPortRange#parse logic does not support IPv6 addresses, fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13556) .NET: Thin client: Transactions support async
Sergey Stronchinskiy created IGNITE-13556: - Summary: .NET: Thin client: Transactions support async Key: IGNITE-13556 URL: https://issues.apache.org/jira/browse/IGNITE-13556 Project: Ignite Issue Type: Improvement Components: platforms, thin client Affects Versions: 2.10 Reporter: Sergey Stronchinskiy Currently are handled via `ThreadLocal` which does not support async flow. -- This message was sent by Atlassian Jira (v8.3.4#803005)
