[jira] [Created] (IGNITE-13391) Ignite-hibernate doesn't recreate cache proxies after full reconnect to the cluster
Evgenii Zhuravlev created IGNITE-13391: -- Summary: Ignite-hibernate doesn't recreate cache proxies after full reconnect to the cluster Key: IGNITE-13391 URL: https://issues.apache.org/jira/browse/IGNITE-13391 Project: Ignite Issue Type: Bug Components: hibernate Affects Versions: 2.7.6 Reporter: Evgenii Zhuravlev If there is only one server node in the cluster and user restart it, client node reconnects to the completely new cluster and, in order to continue using the ignite-hibernate integration, it should recreate all the cache proxies. Otherwise, it leads to the issue described in this thread: http://apache-ignite-users.70518.x6.nabble.com/Hibernate-2nd-Level-query-cache-with-Ignite-td33816.html We should add proxies reinitialization on reconnect. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-12809) Python client returns fields in wrong order since the 2 row when fields_count>10
Evgenii Zhuravlev created IGNITE-12809:
--
Summary: Python client returns fields in wrong order since the 2
row when fields_count>10
Key: IGNITE-12809
URL: https://issues.apache.org/jira/browse/IGNITE-12809
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.8
Reporter: Evgenii Zhuravlev
Attachments: reproducer.py
Reproducer attached.
If result set is bigger than a page size(1 by default) and there are more than
10 fields in an object, then, for all rows after the first query column order
will be wrong.
The reason for that is a sorting in api/sql.py:
https://github.com/apache/ignite/blob/master/modules/platforms/python/pyignite/api/sql.py#L445
If you remove it, everything will work fine. We need to make sure that this is
the right solution for this issue.
Output from reproducer:
{code:java}
['CODE', 'NAME', 'CONTINENT', 'REGION', 'SURFACEAREA', 'INDEPYEAR',
'POPULATION', 'LIFEEXPECTANCY', 'GNP', 'GNPOLD', 'LOCALNAME', 'GOVERNMENTFORM',
'HEADOFSTATE', 'CAPITAL', 'CODE2']
['CHN', 'China', 'Asia', 'Eastern Asia', Decimal('9.5729E+6'), -1523,
1277558000, Decimal('71.4'), Decimal('982268'), Decimal('917719'), 'Zhongquo',
'PeoplesRepublic', 'Jiang Zemin', 1891, 'CN']
['IND', 'India', 'Bharat/India', 'Federal Republic', 'Kocheril Raman
Narayanan', 1109, 'IN', 'Asia', 'Southern and Central Asia',
Decimal('3287263'), 1947, 1013662000, Decimal('62.5'), Decimal('447114'),
Decimal('430572')]
['USA', 'United States', 'United States', 'Federal Republic', 'George W. Bush',
3813, 'US', 'North America', 'North America', Decimal('9.36352E+6'), 1776,
278357000, Decimal('77.1'), Decimal('8.5107E+6'), Decimal('8.1109E+6')]
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-12032) Server node prints exception when ODBC driver disconnects
Evgenii Zhuravlev created IGNITE-12032:
--
Summary: Server node prints exception when ODBC driver disconnects
Key: IGNITE-12032
URL: https://issues.apache.org/jira/browse/IGNITE-12032
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 2.7.5
Reporter: Evgenii Zhuravlev
Whenever a process using ODBC clients is finished, it's printing in the
node logs this exception:
{code:java}
*[07:45:19,559][SEVERE][grid-nio-worker-client-listener-1-#30][ClientListenerProcessor]
Failed to process selector key [s
es=GridSelectorNioSessionImpl [worker=ByteBufferNioClientWorker
[readBuf=java.nio.HeapByteBuffer[pos=0 lim=8192 cap=8192
], super=AbstractNioClientWorker [idx=1, bytesRcvd=0, bytesSent=0,
bytesRcvd0=0, bytesSent0=0, select=true, super=GridWo
rker [name=grid-nio-worker-client-listener-1, igniteInstanceName=null,
finished=false, heartbeatTs=1564289118230, hashCo
de=1829856117, interrupted=false,
runner=grid-nio-worker-client-listener-1-#30]]], writeBuf=null,
readBuf=null, inRecove
ry=null, outRecovery=null, super=GridNioSessionImpl
[locAddr=/0:0:0:0:0:0:0:1:10800, rmtAddr=/0:0:0:0:0:0:0:1:63697, cre
ateTime=1564289116225, closeTime=0, bytesSent=1346, bytesRcvd=588,
bytesSent0=0, bytesRcvd0=0, sndSchedTime=156428911623
5, lastSndTime=1564289116235, lastRcvTime=1564289116235, readsPaused=false,
filterChain=FilterChain[filters=[GridNioAsyn
cNotifyFilter, GridNioCodecFilter [parser=ClientListenerBufferedParser,
directMode=false]], accepted=true, markedForClos
e=false]]]
java.io.IOException: An existing connection was forcibly closed by the
remote host
at sun.nio.ch.SocketDispatcher.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:43)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:197)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at
org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:11
04)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNi
oServer.java:2389)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:215
6)
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1797)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at java.lang.Thread.run(Thread.java:748)*
{code}
It's absolutely normal behavior when ODBC client disconnects from the node, so,
we shouldn't print exception in the log. We should replace it with something
like INFO message about ODBC client disconnection.
Thread from user list:
http://apache-ignite-users.70518.x6.nabble.com/exceptions-in-Ignite-node-when-a-thin-client-process-ends-td28970.html
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-11847) Change note on the capacity planning page about memory usage
Evgenii Zhuravlev created IGNITE-11847: -- Summary: Change note on the capacity planning page about memory usage Key: IGNITE-11847 URL: https://issues.apache.org/jira/browse/IGNITE-11847 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev https://apacheignite.readme.io/docs/capacity-planning#calculating-memory-usage It says that "Apache Ignite will typically add around 200 bytes overhead to each entry.", but it's not true, I think it was applicable only for 1.x versions, where everything was stored in heap -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11832) Creating cache with EvictionPolicy and without onHeap cache kills the cluster
Evgenii Zhuravlev created IGNITE-11832: -- Summary: Creating cache with EvictionPolicy and without onHeap cache kills the cluster Key: IGNITE-11832 URL: https://issues.apache.org/jira/browse/IGNITE-11832 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev After this, the cluster can be restored only by deleting the folder with the problem cache. We should add some kind of validation to avoid these situations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11831) Eviction doesn't work properly for data region with big objects of different sizes
Evgenii Zhuravlev created IGNITE-11831:
--
Summary: Eviction doesn't work properly for data region with big
objects of different sizes
Key: IGNITE-11831
URL: https://issues.apache.org/jira/browse/IGNITE-11831
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
Reproducer:
{code:java}
public class ExampleNodeStartup {
/**
* Start up an empty node with example compute configuration.
*
* @param args Command line arguments, none required.
* @throws IgniteException If failed.
*/
public static void main(String[] args) throws IgniteException {
Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
IgniteCache keywordCache =
ignite.getOrCreateCache("keyword");
for(int i=0;i<1000;i++){
int mega = new Random().nextInt(3) + 1;
keywordCache.put(UUID.randomUUID().toString(), new byte[mega * 1024
* 1024]);
System.out.println("current:"+i);
}
}
}
{code}
data region configuration:
{code:java}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11830) Visor cmd shows up time in HH:MM:SS format
Evgenii Zhuravlev created IGNITE-11830: -- Summary: Visor cmd shows up time in HH:MM:SS format Key: IGNITE-11830 URL: https://issues.apache.org/jira/browse/IGNITE-11830 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Attachments: visor_uptime.png In Visor.scala it takes X.timeSpan2HMS(m.getUpTime), which lead to the behavior, that it starts to count starting from 00:00:00 after a day up time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11696) Create JMX metric for current PME execution time
Evgenii Zhuravlev created IGNITE-11696: -- Summary: Create JMX metric for current PME execution time Key: IGNITE-11696 URL: https://issues.apache.org/jira/browse/IGNITE-11696 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Now PME process can't be monitored from JMX, only from the logs. It makes sense to show the execution time for the current partition map exchange. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11695) AverageGetTime metric doesn't work properly with ScanQuery predicate
Evgenii Zhuravlev created IGNITE-11695:
--
Summary: AverageGetTime metric doesn't work properly with
ScanQuery predicate
Key: IGNITE-11695
URL: https://issues.apache.org/jira/browse/IGNITE-11695
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
In *GridCacheQueryManager.advance* method *start* variable is set only once, at
the start of executing the method, while metrics.onRead inside this method
could be executed multiple times in case if Predicate returns false:
Reproducer:
{code:java}
public class ExampleNodeStartup {
private static int FILTER_COUNT = 10;
/**
* Start up an empty node with example compute configuration.
*
* @param args Command line arguments, none required.
* @throws IgniteException If failed.
*/
public static void main(String[] args) throws IgniteException {
Ignite ignite = Ignition.start();
IgniteCache cache = ignite.getOrCreateCache(new
CacheConfiguration<>("test").setStatisticsEnabled(true));
for (int i = 0; i < 10; i++)
cache.put(i, i);
long start = System.currentTimeMillis();
Iterator it = cache.query(new ScanQuery().setFilter(new
IgniteBiPredicate() {
@Override public boolean apply(Object o, Object o2) {
if ((int)o2 % FILTER_COUNT == 0)
return true;
return false;
}
})).iterator();
while (it.hasNext())
System.out.println("iterator value: " + it.next());
System.out.println("Execution time: " + (System.currentTimeMillis() -
start));
System.out.println("GETS: " + cache.metrics().getCacheGets());
System.out.println("GET times: " + cache.metrics().getAverageGetTime());
}
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11610) Add note to the DROP TABLE doc that it can be used only for table created with DDL
Evgenii Zhuravlev created IGNITE-11610: -- Summary: Add note to the DROP TABLE doc that it can be used only for table created with DDL Key: IGNITE-11610 URL: https://issues.apache.org/jira/browse/IGNITE-11610 Project: Ignite Issue Type: Bug Components: documentation Reporter: Evgenii Zhuravlev Assignee: Artem Budnikov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11599) Thin client doesn't have proper retry
Evgenii Zhuravlev created IGNITE-11599:
--
Summary: Thin client doesn't have proper retry
Key: IGNITE-11599
URL: https://issues.apache.org/jira/browse/IGNITE-11599
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
In case when one of the nodes from the addresses list is nor available, there
is a chance that you will see "Ignite cluster is unavailable" even if other
nodes are running.
{code:java}
List addrs = new ArrayList(2);
addrs.add("127.0.0.1:10800");
addrs.add("127.0.0.1:10801");
ClientConfiguration cfg = new
ClientConfiguration().setAddresses(addrs.toArray(new String[]{}));
IgniteClient igniteClient = Ignition.startClient(cfg)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11598) Add possibility to have different rebalance thread pool size for nodes in cluster
Evgenii Zhuravlev created IGNITE-11598: -- Summary: Add possibility to have different rebalance thread pool size for nodes in cluster Key: IGNITE-11598 URL: https://issues.apache.org/jira/browse/IGNITE-11598 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev It can be used for changing this property without downtime when rebalance is slow -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11554) Create detailed documentation for peerClassLoading with places where and how it can be used
Evgenii Zhuravlev created IGNITE-11554: -- Summary: Create detailed documentation for peerClassLoading with places where and how it can be used Key: IGNITE-11554 URL: https://issues.apache.org/jira/browse/IGNITE-11554 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Evgenii Zhuravlev Right now, it's not clear for which classes and which APIs peerClassLoading works. Also, we should describe some of the examples of use cases for peerClassLoading -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11496) Long running SQL queries could be randomly canceled from WC
Evgenii Zhuravlev created IGNITE-11496: -- Summary: Long running SQL queries could be randomly canceled from WC Key: IGNITE-11496 URL: https://issues.apache.org/jira/browse/IGNITE-11496 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev I've tried to run some long-running queries from WC(more than a couple of minutes) and I've faced a behavior when the query was canceled without clicking on the cancel button. I've opened different browser tabs at this moment, maybe it could be the reason. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11495) document IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE parameter
Evgenii Zhuravlev created IGNITE-11495: -- Summary: document IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE parameter Key: IGNITE-11495 URL: https://issues.apache.org/jira/browse/IGNITE-11495 Project: Ignite Issue Type: Improvement Components: documentation, sql Affects Versions: 2.7 Reporter: Evgenii Zhuravlev Assignee: Artem Budnikov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11494) Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter
Evgenii Zhuravlev created IGNITE-11494: -- Summary: Change message log message in case of too small IGNITE_SQL_MERGE_TABLE_MAX_SIZE parameter Key: IGNITE-11494 URL: https://issues.apache.org/jira/browse/IGNITE-11494 Project: Ignite Issue Type: Improvement Components: sql Reporter: Evgenii Zhuravlev Message "Fetched result set was too large." should be changed to some recommendations regarding IGNITE_SQL_MERGE_TABLE_MAX_SIZE property -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11487) Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property
Evgenii Zhuravlev created IGNITE-11487: -- Summary: Document IGNITE_SQL_MERGE_TABLE_MAX_SIZE property Key: IGNITE-11487 URL: https://issues.apache.org/jira/browse/IGNITE-11487 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Evgenii Zhuravlev Assignee: Prachi Garg -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11373) varchar_ignorecase doesn't work properly
Evgenii Zhuravlev created IGNITE-11373:
--
Summary: varchar_ignorecase doesn't work properly
Key: IGNITE-11373
URL: https://issues.apache.org/jira/browse/IGNITE-11373
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
Looks like a field with type varchar_ignorecase can't be used for filtering the
values for different cases.
{code:java}
Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
IgniteCache cache = ignite.getOrCreateCache("TEST");
cache.query(new SqlFieldsQuery("CREATE TABLE IF NOT EXISTS TEST\n" +
"(\n" +
" TEST_IDNUMBER(15)NOT NULL,\n" +
" TEST_VALUE VARCHAR_IGNORECASE(100),\n" +
" PRIMARY KEY (TEST_ID)\n" +
") "));
System.out.println("INSERTED:" + ignite.cache("TEST").query(new
SqlFieldsQuery("INSERT INTO TEST values (1,'aAa')")).getAll().size());
System.out.println("FOUND:" + ignite.cache("TEST").query(new
SqlFieldsQuery("Select * from TEST where TEST_VALUE like
'%aaa%'")).getAll().size());
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11219) CREATE TABLE with template doesn't work properly with data inserted from KV API
Evgenii Zhuravlev created IGNITE-11219:
--
Summary: CREATE TABLE with template doesn't work properly with
data inserted from KV API
Key: IGNITE-11219
URL: https://issues.apache.org/jira/browse/IGNITE-11219
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
When you use a template for your table, it takes the affinityMapper field from
this template, which was set for a different type without any
keyConfigurations. This leads to the problem with accessing data from SQL if
it was inserted using Key-value API
Here is a code to reproduce the issue:
{code:java}
Ignition.setClientMode(true);
Ignite ignite = Ignition.start("examples/config/example-ignite.xml");
ignite.cluster().active(true);
IgniteCache cache = ignite.getOrCreateCache("test");
cache.query(new SqlFieldsQuery("CREATE TABLE IF NOT EXISTS TEST\n" +
"(\n" +
" TEST_IDNUMBER(15)NOT NULL,\n" +
" TEST_FIELD VARCHAR2(100),\n" +
" PRIMARY KEY (TEST_ID)\n" +
") with \"TEMPLATE=TEST_TEMPLATE,KEY_TYPE=TEST_KEY
,CACHE_NAME=TEST_CACHE ,
VALUE_TYPE=TEST_VALUE,ATOMICITY=TRANSACTIONAL\";").setSchema("PUBLIC"));
for (int i = 0; i < 100; i++) {
BinaryObjectBuilder keyBuilder =
ignite.binary().builder("TEST_KEY");
keyBuilder.setField("TEST_ID", new BigDecimal(111l +
i));
BinaryObjectBuilder valueBuilder =
ignite.binary().builder("TEST_VALUE");
valueBuilder.setField("TEST_FIELD", "123123" + i);
ignite.cache("TEST_CACHE").withKeepBinary().put(keyBuilder.build(),
valueBuilder.build());
}
System.out.println("FOUND:" + ignite.cache("TEST_CACHE").query(new
SqlFieldsQuery("Select * from TEST")).getAll().size());
System.out.println("FOUND:" + ignite.cache("TEST_CACHE").query(new
SqlFieldsQuery("Select TEST_FIELD from TEST where TEST_ID =
111")).getAll());
for (int i = 0; i < 100; i++)
System.out.println("FOUND:" + ignite.cache("TEST_CACHE").query(new
SqlFieldsQuery("Select TEST_FIELD from TEST where TEST_ID = " +
(111l + i))).getAll());
{code}
Here is a test template:
{code:java}
{code}
Steps to reproduce:
1. Start a server node, for example, using ExampleNodeStartup.
2. Start a client node using the code provided above with the template in
configuration.
Possible quickfix:
set affinityMapper to cfgTemplate in GridCacheProcessor.getConfigFromTemplate:
cfgTemplate.setAffinityMapper(null)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11165) Add note to the documentation that cache name will be used as folder name in case of using persistence
Evgenii Zhuravlev created IGNITE-11165: -- Summary: Add note to the documentation that cache name will be used as folder name in case of using persistence Key: IGNITE-11165 URL: https://issues.apache.org/jira/browse/IGNITE-11165 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Evgenii Zhuravlev Assignee: Artem Budnikov We should add a note that it's not recommended to use symbols which are not allowed to use in the file system in case of using persistence. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11096) Webagent: flag --disable-demo doesn't work
Evgenii Zhuravlev created IGNITE-11096: -- Summary: Webagent: flag --disable-demo doesn't work Key: IGNITE-11096 URL: https://issues.apache.org/jira/browse/IGNITE-11096 Project: Ignite Issue Type: Bug Components: wizards Affects Versions: 2.7 Environment: After enabling this flag it's still possible to start demo Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11052) Add documentation for "failed to wait for partition map exchange" message
Evgenii Zhuravlev created IGNITE-11052: -- Summary: Add documentation for "failed to wait for partition map exchange" message Key: IGNITE-11052 URL: https://issues.apache.org/jira/browse/IGNITE-11052 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Evgenii Zhuravlev Assignee: Denis Magda We should describe why this message could be seen in logs and how to debug the real problem that caused this message. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11015) AveragePutTime metrics doesn't work properly in case of remote puts
Evgenii Zhuravlev created IGNITE-11015: -- Summary: AveragePutTime metrics doesn't work properly in case of remote puts Key: IGNITE-11015 URL: https://issues.apache.org/jira/browse/IGNITE-11015 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev It happens because the number of writes is collected on the server machine, while execution time is collected on the machine which invoked the operation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10838) Ignite wrap byte[] value with UserCacheObjectByteArrayImpl before saving it and copying the whole array
Evgenii Zhuravlev created IGNITE-10838: -- Summary: Ignite wrap byte[] value with UserCacheObjectByteArrayImpl before saving it and copying the whole array Key: IGNITE-10838 URL: https://issues.apache.org/jira/browse/IGNITE-10838 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev I assume it was created for heap cache before 2.0, while it doesn't make sense for off-heap cache since it will be copied in any case. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10734) Add documentation for the list of operations that should be retried in case of cluster topology changes
Evgenii Zhuravlev created IGNITE-10734: -- Summary: Add documentation for the list of operations that should be retried in case of cluster topology changes Key: IGNITE-10734 URL: https://issues.apache.org/jira/browse/IGNITE-10734 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Assignee: Artem Budnikov Some of the operations, like get or getAll would throw ClusterTopologyException if primary node left topology, while other operations not. So, some operations should be re-tried from user code, while some operation will do it internally. We should prepare documentation for the list of these operations. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10627) Support custom preferences like date format and other similar features
Evgenii Zhuravlev created IGNITE-10627: -- Summary: Support custom preferences like date format and other similar features Key: IGNITE-10627 URL: https://issues.apache.org/jira/browse/IGNITE-10627 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10626) Save authenticated Webconsole session for more than one page refresh
Evgenii Zhuravlev created IGNITE-10626: -- Summary: Save authenticated Webconsole session for more than one page refresh Key: IGNITE-10626 URL: https://issues.apache.org/jira/browse/IGNITE-10626 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Now, it's needed to enter login and password after each page refresh -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10414) IF NOT EXISTS in CREATE TABLE doesn't work
Evgenii Zhuravlev created IGNITE-10414:
--
Summary: IF NOT EXISTS in CREATE TABLE doesn't work
Key: IGNITE-10414
URL: https://issues.apache.org/jira/browse/IGNITE-10414
Project: Ignite
Issue Type: Bug
Components: sql
Affects Versions: 2.4
Reporter: Evgenii Zhuravlev
Reproducer:
{code:java}
Ignite ignite = Ignition.start();
ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE TABLE
IF NOT EXISTS City(id LONG PRIMARY KEY,"
+ " name VARCHAR) WITH \"template=replicated\""));
ignite.getOrCreateCache("test").query(new SqlFieldsQuery("CREATE TABLE
IF NOT EXISTS City(id LONG PRIMARY KEY,"
+ " name VARCHAR) WITH \"template=replicated\""));
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10398) CacheMetrics always return 0 for local cache
Evgenii Zhuravlev created IGNITE-10398:
--
Summary: CacheMetrics always return 0 for local cache
Key: IGNITE-10398
URL: https://issues.apache.org/jira/browse/IGNITE-10398
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
However, it shows the right offHeapEntriesCnt.
Short code snippet:
{code:java}
IgniteConfiguration igniteConfig = new IgniteConfiguration();
CacheConfiguration cacheConfig = new CacheConfiguration("testCache");
cacheConfig.setStatisticsEnabled(true);
igniteConfig.setCacheConfiguration(cacheConfig);
cacheConfig.setCacheMode(CacheMode.LOCAL);
try (Ignite ignite = Ignition.start(igniteConfig)) {
IgniteCache cache = ignite.getOrCreateCache(cacheConfig.getName());
cache.put("key", "val");
cache.put("key2", "val2");
cache.remove("key2");
System.out.println(cache.localMetrics());
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9657) socket leak in TcpDiscoverySpi
Evgenii Zhuravlev created IGNITE-9657: - Summary: socket leak in TcpDiscoverySpi Key: IGNITE-9657 URL: https://issues.apache.org/jira/browse/IGNITE-9657 Project: Ignite Issue Type: Bug Affects Versions: 2.6 Reporter: Evgenii Zhuravlev Assignee: Evgenii Zhuravlev Fix For: 2.7 When host from ipFinder can't be resolved, the socket don't close -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9486) JobStealing doesn't work with affinityRun
Evgenii Zhuravlev created IGNITE-9486:
-
Summary: JobStealing doesn't work with affinityRun
Key: IGNITE-9486
URL: https://issues.apache.org/jira/browse/IGNITE-9486
Project: Ignite
Issue Type: Bug
Affects Versions: 2.6
Reporter: Evgenii Zhuravlev
It rebalances job to the node, that doesn't have needed partition, which lead
to the exception:
{code:java}
[2018-09-06 18:03:47,545][ERROR][pub-#61][GridJobWorker] Failed to lock
partitions [jobId=a29f86fa561-3e2c91e1-1f47-401c-80a2-ea2b452a3cb5,
ses=GridJobSessionImpl [ses=GridTaskSessionImpl
[taskName=o.a.i.examples.ExampleNodeStartup3$1, dep=GridDeployment
[ts=1536246214786, depMode=SHARED,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2,
clsLdrId=606b86fa561-cffc6951-7eef-4a58-82e1-69511458d650, userVer=0, loc=true,
sampleClsName=o.a.i.i.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap,
pendingUndeploy=false, undeployed=false, usage=1],
taskClsName=o.a.i.examples.ExampleNodeStartup3$1,
sesId=929f86fa561-3e2c91e1-1f47-401c-80a2-ea2b452a3cb5,
startTime=1536246223300, endTime=9223372036854775807,
taskNodeId=3e2c91e1-1f47-401c-80a2-ea2b452a3cb5,
clsLdr=sun.misc.Launcher$AppClassLoader@18b4aac2, closed=false, cpSpi=null,
failSpi=null, loadSpi=null, usage=1, fullSup=false, internal=false,
topPred=null, subjId=3e2c91e1-1f47-401c-80a2-ea2b452a3cb5, mapFut=IgniteFuture
[orig=GridFutureAdapter [ignoreInterrupts=false, state=INIT, res=null,
hash=30355072]], execName=null],
jobId=a29f86fa561-3e2c91e1-1f47-401c-80a2-ea2b452a3cb5]]
class org.apache.ignite.IgniteException: Failed partition reservation.
Partition is not primary on the node. [partition=1, cacheName=test,
nodeId=cffc6951-7eef-4a58-82e1-69511458d650, topology=AffinityTopologyVersion
[topVer=3, minorTopVer=0]]
at
org.apache.ignite.internal.processors.job.GridJobProcessor$PartitionsReservation.reserve(GridJobProcessor.java:1596)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:510)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
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)
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9383) Add to the documentation that Ignite cluster requires that each nodes have direct connection to any nodes of grid.
Evgenii Zhuravlev created IGNITE-9383: - Summary: Add to the documentation that Ignite cluster requires that each nodes have direct connection to any nodes of grid. Key: IGNITE-9383 URL: https://issues.apache.org/jira/browse/IGNITE-9383 Project: Ignite Issue Type: Improvement Components: documentation Affects Versions: 2.6 Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9199) Ignite doesn't save history for SQL queries after setting queryDetailMetricsSize
Evgenii Zhuravlev created IGNITE-9199: - Summary: Ignite doesn't save history for SQL queries after setting queryDetailMetricsSize Key: IGNITE-9199 URL: https://issues.apache.org/jira/browse/IGNITE-9199 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Steps to reproduce: 1. Start cluster with persistence without queryDetailMetricsSize. 2. Restart cluster with configured queryDetailMetricsSize. Ignite save history for SCAN queries only. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9153) Accessing cache from transaction on client node, where it was not accessed yet throws an exception
Evgenii Zhuravlev created IGNITE-9153: - Summary: Accessing cache from transaction on client node, where it was not accessed yet throws an exception Key: IGNITE-9153 URL: https://issues.apache.org/jira/browse/IGNITE-9153 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Attachments: ClientCacheTransactionsTest.java Exception message: Cannot start/stop cache within lock or transaction. Reproducer is attached: ClientCacheTransactionsTest.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9052) Add possibility to configure Ignite instance name for springData repository in IgniteRepositoryFactoryBean
Evgenii Zhuravlev created IGNITE-9052: - Summary: Add possibility to configure Ignite instance name for springData repository in IgniteRepositoryFactoryBean Key: IGNITE-9052 URL: https://issues.apache.org/jira/browse/IGNITE-9052 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev This configuration can be used to access 2 different clusters from 2 repositories in one spring context -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9019) Ignite prints redundant warnings on node start
Evgenii Zhuravlev created IGNITE-9019: - Summary: Ignite prints redundant warnings on node start Key: IGNITE-9019 URL: https://issues.apache.org/jira/browse/IGNITE-9019 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev It's scary to see so many warnings when you start node with default configuration: [WARN ][main][TcpCommunicationSpi] Message queue limit is set to 0 which may lead to potential OOMEs when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to message queues growth on sender and receiver sides. [WARN ][main][NoopCheckpointSpi] Checkpoints are disabled (to enable configure any GridCheckpointSpi implementation) [WARN ][main][GridCollisionManager] Collision resolution is disabled (all jobs will be activated upon arrival). [WARN ][main][IgniteKernal] Peer class loading is enabled (disable it in production for performance and deployment consistency reasons) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9016) Byte arrays are not working as cache keys
Evgenii Zhuravlev created IGNITE-9016:
-
Summary: Byte arrays are not working as cache keys
Key: IGNITE-9016
URL: https://issues.apache.org/jira/browse/IGNITE-9016
Project: Ignite
Issue Type: Bug
Reporter: Evgenii Zhuravlev
it's not possible to retrieve early inserted data with byte[] key:
{code:java}
IgniteCache cache = ignite.getOrCreateCache("test");
byte[] a = "test".getBytes();
cache.put(a, a);
cache.get(a); //returns null
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8934) LongJVMPauseDetector prints error on thread interruption when node stopping
Evgenii Zhuravlev created IGNITE-8934: - Summary: LongJVMPauseDetector prints error on thread interruption when node stopping Key: IGNITE-8934 URL: https://issues.apache.org/jira/browse/IGNITE-8934 Project: Ignite Issue Type: Bug Affects Versions: 2.5 Reporter: Evgenii Zhuravlev Assignee: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8899) IgniteJdbcDriver directly create JavaLogger in static context
Evgenii Zhuravlev created IGNITE-8899: - Summary: IgniteJdbcDriver directly create JavaLogger in static context Key: IGNITE-8899 URL: https://issues.apache.org/jira/browse/IGNITE-8899 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev It means, that it always prints error in logs, if Jul logging file doesn't exist. I suggest to use the same approach as in thin driver: replace new JavaLogger() with Logger.getLogger(IgniteJdbcDriver.class.getName()) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8810) Create failoverSafe for ReentrantLock
Evgenii Zhuravlev created IGNITE-8810: - Summary: Create failoverSafe for ReentrantLock Key: IGNITE-8810 URL: https://issues.apache.org/jira/browse/IGNITE-8810 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Currently, it has the flag "failoverSafe", but it doesn't have any implementation for it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8433) Upgrade zookeper version
Evgenii Zhuravlev created IGNITE-8433: - Summary: Upgrade zookeper version Key: IGNITE-8433 URL: https://issues.apache.org/jira/browse/IGNITE-8433 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev AI 2.4.0 internally uses zookeeper 3.4.6 and this version of zookeeper uses netty 3.7.0.Final. This version of Netty had reported a security vulnerability CVE-2014-3488 that was addressed in later versions and zookeeper has upgraded netty in later versions such as 3.4.10. But the latest version of Ignite 2.4.0 is still using zookeeper 3.4.6 Â http://apache-ignite-users.70518.x6.nabble.com/Ignite-latest-release-using-zookeeper-3-4-6-td21382.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8426) Some classes creates JavaLogger directly which lead to SEVERE message in logs if JUL config file is missing
Evgenii Zhuravlev created IGNITE-8426: - Summary: Some classes creates JavaLogger directly which lead to SEVERE message in logs if JUL config file is missing Key: IGNITE-8426 URL: https://issues.apache.org/jira/browse/IGNITE-8426 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Here is the error message: SEVERE: Failed to resolve default logging config file: config/java.util.logging.properties For example, problem code is placed in LongJVMPauseDetector and IgniteJdbcDriver classes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8230) SQL: CREATE TABLE doesn't take backups from template
Evgenii Zhuravlev created IGNITE-8230: - Summary: SQL: CREATE TABLE doesn't take backups from template Key: IGNITE-8230 URL: https://issues.apache.org/jira/browse/IGNITE-8230 Project: Ignite Issue Type: Bug Components: sql Affects Versions: 2.4 Reporter: Evgenii Zhuravlev Fix For: 2.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7928) Exception is not propagated to the C# client and the app hangs
Evgenii Zhuravlev created IGNITE-7928:
-
Summary: Exception is not propagated to the C# client and the app
hangs
Key: IGNITE-7928
URL: https://issues.apache.org/jira/browse/IGNITE-7928
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.3
Reporter: Evgenii Zhuravlev
An exception like https://issues.apache.org/jira/browse/IGNITE-1903 is not
propagated to the C# client:
the issue has happened during JNI call, that is why .NET hung.
The marshaller is unable to unmarshal CacheStoreFactory class (it is absent on
the client node).
Â
Stack trace:
Â
{code:java}
class org.apache.ignite.IgniteException: Platform
error:System.ArgumentNullException: Value cannot be null. Parameter name: key Â
 at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument) Â
 at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)   at
System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value) Â Â
at Apache.Ignite.Core.Impl.Binary.Marshaller.GetDescriptor(Type type) Â Â at
Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadFullObject[T](Int32 pos, Type
typeOverride) Â Â at
Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
typeOverride) Â Â at
Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride) Â
 at Apache.Ignite.Core.Impl.Binary.BinaryReader.ReadBinaryObject[T](Boolean
doDetach) Â Â at
Apache.Ignite.Core.Impl.Binary.BinaryReader.TryDeserialize[T](T& res, Type
typeOverride) Â Â at
Apache.Ignite.Core.Impl.Binary.BinaryReader.Deserialize[T](Type typeOverride) Â
 at Apache.Ignite.Core.Impl.Cache.Store.CacheStore.CreateInstance(Int64 memPtr,
HandleRegistry registry) Â Â at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.CacheStoreCreate(Int64
memPtr) Â Â at
Apache.Ignite.Core.Impl.Unmanaged.UnmanagedCallbacks.InLongOutLong(Void*
target, Int32 type, Int64 val) Â Â Â Â at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.loggerLog(PlatformProcessorImpl.java:373)
    at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:423)
    at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.processInStreamOutLong(PlatformProcessorImpl.java:434)
    at
org.apache.ignite.internal.processors.platform.PlatformTargetProxyImpl.inStreamOutLong(PlatformTargetProxyImpl.java:67)
    at
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.inLongOutLong(Native
Method) Â Â Â Â at
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.cacheStoreCreate(PlatformCallbackGateway.java:65)
    at
org.apache.ignite.internal.processors.platform.dotnet.PlatformDotNetCacheStore.initialize(PlatformDotNetCacheStore.java:403)
    at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.registerStore0(PlatformProcessorImpl.java:650)
    at
org.apache.ignite.internal.processors.platform.PlatformProcessorImpl.registerStore(PlatformProcessorImpl.java:293)
    at
org.apache.ignite.internal.processors.cache.store.CacheOsStoreManager.start0(CacheOsStoreManager.java:60)
    at
org.apache.ignite.internal.processors.cache.GridCacheManagerAdapter.start(GridCacheManagerAdapter.java:50)
    at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1097)
    at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1826)
    at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCacheStartRequests(CacheAffinitySharedManager.java:428)
    at
org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.processClientCachesChanges(CacheAffinitySharedManager.java:611)
    at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.processCustomExchangeTask(GridCacheProcessor.java:338)
    at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.processCustomTask(GridCachePartitionExchangeManager.java:2142)
    at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2231)
    at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) Â Â Â
 at java.lang.Thread.run(Thread.java:748){code}
Â
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-7614) Documentation: How to access data from key-value that was inserted from SQL
Evgenii Zhuravlev created IGNITE-7614: - Summary: Documentation: How to access data from key-value that was inserted from SQL Key: IGNITE-7614 URL: https://issues.apache.org/jira/browse/IGNITE-7614 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Evgenii Zhuravlev Assignee: Denis Magda Fix For: 2.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7555) Create documentation for using Ignite Persistence on Kubernetes
Evgenii Zhuravlev created IGNITE-7555: - Summary: Create documentation for using Ignite Persistence on Kubernetes Key: IGNITE-7555 URL: https://issues.apache.org/jira/browse/IGNITE-7555 Project: Ignite Issue Type: Task Components: documentation Reporter: Evgenii Zhuravlev Fix For: 2.5 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7512) Variable updated should be checked for null before invocation of ctx.validateKeyAndValue(entry.key(), updated) in GridDhtAtomicCache.updateWithBatch
Evgenii Zhuravlev created IGNITE-7512: - Summary: Variable updated should be checked for null before invocation of ctx.validateKeyAndValue(entry.key(), updated) in GridDhtAtomicCache.updateWithBatch Key: IGNITE-7512 URL: https://issues.apache.org/jira/browse/IGNITE-7512 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Or it could lead to the NPE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7361) HA: NPE in HadoopJobTracker.jobMetaCache
Evgenii Zhuravlev created IGNITE-7361: - Summary: HA: NPE in HadoopJobTracker.jobMetaCache Key: IGNITE-7361 URL: https://issues.apache.org/jira/browse/IGNITE-7361 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev java.lang.NullPointerException at org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.jobMetaCache(HadoopJobTracker.java:206) at org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.finishFuture(HadoopJobTracker.java:478) at org.apache.ignite.internal.processors.hadoop.HadoopProcessor.finishFuture(HadoopProcessor.java:192) at org.apache.ignite.internal.processors.hadoop.HadoopImpl.finishFuture(HadoopImpl.java:111) at org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolJobStatusTask.run(HadoopProtocolJobStatusTask.java:59) at org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolJobStatusTask.run(HadoopProtocolJobStatusTask.java:33) at org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolTaskAdapter$Job.execute(HadoopProtocolTaskAdapter.java:101) at org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566) at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629) at org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560) at org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181) at org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908) at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1562) at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1190) at org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126) at org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097) [ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152) [?:1.7.0_151] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622) [?:1.7.0_151] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7355) peerClassLoadin doesn't work with DataStreamer Transformer
Evgenii Zhuravlev created IGNITE-7355:
-
Summary: peerClassLoadin doesn't work with DataStreamer Transformer
Key: IGNITE-7355
URL: https://issues.apache.org/jira/browse/IGNITE-7355
Project: Ignite
Issue Type: Bug
Affects Versions: 2.3
Reporter: Evgenii Zhuravlev
Example:
{code:java}
try (IgniteDataStreamer streamer =
ignite.dataStreamer(CacheName.CACHE)) {
streamer.receiver(StreamTransformer.from(new
MyCacheEntryProcessor()));
streamer.addData("key", "value");
}
private static class MyCacheEntryProcessor implements
CacheEntryProcessor {
@Override
public Object process(MutableEntry mutableEntry,
Object... objects) throws EntryProcessorException {
return null;
}
}
{code}
workaround: use streamer.deployClass(MyCacheEntryProcessor.class);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7349) Add possibility to serialise and deserialise IgniteAtomicSequence with custom AtomicConfiguration
Evgenii Zhuravlev created IGNITE-7349: - Summary: Add possibility to serialise and deserialise IgniteAtomicSequence with custom AtomicConfiguration Key: IGNITE-7349 URL: https://issues.apache.org/jira/browse/IGNITE-7349 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev now, if an atomic sequence has AtomicConfiguration with custom groupName, it will lead to the problems. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7289) ODBC: add possibility to reconnect to the cluster after node failing
Evgenii Zhuravlev created IGNITE-7289: - Summary: ODBC: add possibility to reconnect to the cluster after node failing Key: IGNITE-7289 URL: https://issues.apache.org/jira/browse/IGNITE-7289 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Assignee: Igor Sapego -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7180) ODBC: add possibility to configure more than one address in connection string
Evgenii Zhuravlev created IGNITE-7180: - Summary: ODBC: add possibility to configure more than one address in connection string Key: IGNITE-7180 URL: https://issues.apache.org/jira/browse/IGNITE-7180 Project: Ignite Issue Type: Improvement Components: odbc Affects Versions: 2.3 Reporter: Evgenii Zhuravlev Assignee: Igor Sapego -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7114) C++ node can't start without java examples folder
Evgenii Zhuravlev created IGNITE-7114: - Summary: C++ node can't start without java examples folder Key: IGNITE-7114 URL: https://issues.apache.org/jira/browse/IGNITE-7114 Project: Ignite Issue Type: Bug Components: platforms Affects Versions: 2.1 Reporter: Evgenii Zhuravlev Assignee: Igor Sapego Priority: Critical Fix For: 2.4 Error message: ERROR: Java classpath is empty (did you set IGNITE_HOME environment variable?) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7088) Wrong implementation of DIRECT comparator for ordering cache start operations
Evgenii Zhuravlev created IGNITE-7088:
-
Summary: Wrong implementation of DIRECT comparator for ordering
cache start operations
Key: IGNITE-7088
URL: https://issues.apache.org/jira/browse/IGNITE-7088
Project: Ignite
Issue Type: Bug
Affects Versions: 2.3
Reporter: Evgenii Zhuravlev
Priority: Critical
Fix For: 2.4
{code:java}
java.lang.IllegalArgumentException: Comparison method violates its general
contract!
at java.util.TimSort.mergeHi(TimSort.java:899) ~[?:1.8.0_102]
at java.util.TimSort.mergeAt(TimSort.java:516) ~[?:1.8.0_102]
at java.util.TimSort.mergeForceCollapse(TimSort.java:457) ~[?:1.8.0_102]
at java.util.TimSort.sort(TimSort.java:254) ~[?:1.8.0_102]
at java.util.Arrays.sort(Arrays.java:1512) ~[?:1.8.0_102]
at java.util.ArrayList.sort(ArrayList.java:1454) ~[?:1.8.0_102]
at java.util.Collections.sort(Collections.java:175) ~[?:1.8.0_102]
at
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.orderedCaches(ClusterCachesInfo.java:1616)
~[ignite-core-2.1.7.jar:2.1.7]
at
org.apache.ignite.internal.processors.cache.ClusterCachesInfo.cachesReceivedFromJoin(ClusterCachesInfo.java:839)
~[ignite-core-2.1.7.jar:2.1.7]
at
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startReceivedCaches(GridCacheProcessor.java:1709)
~[ignite-core-2.1.7.jar:2.1.7]
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:606)
[ignite-core-2.1.7.jar:2.1.7]
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2278)
[ignite-core-2.1.7.jar:2.1.7]
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
[ignite-core-2.1.7.jar:2.1.7]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
{code}
When 2 not user cache will be compared using this comparator, this above
exception will be thrown.
As a workaround can be used environment variable
-Djava.util.Arrays.useLegacyMergeSort=true
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-6992) Ignite MR problem with accessing hdfs with enabled Kerberos
Evgenii Zhuravlev created IGNITE-6992: - Summary: Ignite MR problem with accessing hdfs with enabled Kerberos Key: IGNITE-6992 URL: https://issues.apache.org/jira/browse/IGNITE-6992 Project: Ignite Issue Type: Bug Affects Versions: 2.3, 2.1, 2.0 Reporter: Evgenii Zhuravlev class org.apache.ignite.IgniteCheckedException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] at org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:169) at org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2Job.initialize(HadoopV2Job.java:328) at org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.job(HadoopJobTracker.java:1141) at org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.submit(HadoopJobTracker.java:318) at org.apache.ignite.internal.processors.hadoop.HadoopProcessor.submit(HadoopProcessor.java:173) at org.apache.ignite.internal.processors.hadoop.HadoopImpl.submit(HadoopImpl.java:69) at org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:50) at org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolSubmitJobTask.run(HadoopProtocolSubmitJobTask.java:33) at org.apache.ignite.internal.processors.hadoop.proto.HadoopProtocolTaskAdapter$Job.execute(HadoopProtocolTaskAdapter.java:101) at org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566) at org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629) at org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560) at org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181) at org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1908) at org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1562) at org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1190) at org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126) at org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622) at java.lang.Thread.run(Thread.java:748) Caused by: org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.apache.hadoop.ipc.RemoteException.instantiateException(RemoteException.java:106) at org.apache.hadoop.ipc.RemoteException.unwrapRemoteException(RemoteException.java:73) at org.apache.hadoop.hdfs.DFSClient.getFileInfo(DFSClient.java:2110) at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1305) at org.apache.hadoop.hdfs.DistributedFileSystem$22.doCall(DistributedFileSystem.java:1301) at org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81) at org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1301) at org.apache.hadoop.fs.FileSystem.exists(FileSystem.java:1426) at org.apache.ignite.internal.processors.hadoop.impl.v2.HadoopV2JobResourceManager.prepareJobEnvironment(HadoopV2JobResourceManager.java:136) ... 22 more Caused by: org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.AccessControlException): SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] at org.apache.hadoop.ipc.Client.call(Client.java:1475) at org.apache.hadoop.ipc.Client.call(Client.java:1412) at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229) at com.sun.proxy.$Proxy36.getFileInfo(Unknown Source) at
[jira] [Created] (IGNITE-6755) Add possibility to create sql tables with DDL without defined PRIMARY KEY, by adding it implicitly
Evgenii Zhuravlev created IGNITE-6755: - Summary: Add possibility to create sql tables with DDL without defined PRIMARY KEY, by adding it implicitly Key: IGNITE-6755 URL: https://issues.apache.org/jira/browse/IGNITE-6755 Project: Ignite Issue Type: Improvement Security Level: Public (Viewable by anyone) Components: sql Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6591) JdbcThinErrorsSelfTest.testBatchUpdateException() should be removed, as batch updates already supported
Evgenii Zhuravlev created IGNITE-6591: - Summary: JdbcThinErrorsSelfTest.testBatchUpdateException() should be removed, as batch updates already supported Key: IGNITE-6591 URL: https://issues.apache.org/jira/browse/IGNITE-6591 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Priority: Trivial -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6533) Jdbc Client friver connection creation could hang if client node can't start in parallel
Evgenii Zhuravlev created IGNITE-6533: - Summary: Jdbc Client friver connection creation could hang if client node can't start in parallel Key: IGNITE-6533 URL: https://issues.apache.org/jira/browse/IGNITE-6533 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Evgenii Zhuravlev 1. Start client node with 2. At the same time create connection with the same configuration in JDBC Client driver 3. If client node won't start, jdbc connection will hang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6365) Wrong EventType and oldValue in RemoteFilter of CQ on not primary node due to reordering after EntryProcessor update
Evgenii Zhuravlev created IGNITE-6365: - Summary: Wrong EventType and oldValue in RemoteFilter of CQ on not primary node due to reordering after EntryProcessor update Key: IGNITE-6365 URL: https://issues.apache.org/jira/browse/IGNITE-6365 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Example of events: IS PRIMARY NODE: true EVENT:CacheContinuousQueryEvent [evtType=UPDATED, key=4, newVal=2061, oldVal=2060] IS PRIMARY NODE: true EVENT:CacheContinuousQueryEvent [evtType=UPDATED, key=4, newVal=2062, oldVal=2061] IS PRIMARY NODE: false EVENT:CacheContinuousQueryEvent [evtType=UPDATED, key=4, newVal=2062, oldVal=2060] IS PRIMARY NODE: false EVENT:CacheContinuousQueryEvent [evtType=CREATED, key=4, newVal=2061, oldVal=null] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6345) Wrong message about cluster activation
Evgenii Zhuravlev created IGNITE-6345: - Summary: Wrong message about cluster activation Key: IGNITE-6345 URL: https://issues.apache.org/jira/browse/IGNITE-6345 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Evgenii Zhuravlev Priority: Minor Fix For: 2.3 Message of an exception that threw while performing an operation on inactive cluster relates to method Ignite.activate(true), which doesn't exist. Method in message should be changed to Ignite.active(true) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6248) Check Java 7 builds for compatibility with Ignite and update documentation
Evgenii Zhuravlev created IGNITE-6248: - Summary: Check Java 7 builds for compatibility with Ignite and update documentation Key: IGNITE-6248 URL: https://issues.apache.org/jira/browse/IGNITE-6248 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Evgenii Zhuravlev Priority: Minor According to some threads on SO and user list, some old Java 7 version doesn't compatible with Ignite since version 2.1 anymore: http://apache-ignite-users.70518.x6.nabble.com/Caused-by-org-h2-jdbc-JdbcSQLException-General-error-quot-java-lang-IllegalMonitorStateException-Attt-td15684.html https://stackoverflow.com/questions/45911616/datastreamer-does-not-work-well/45972341#45972341 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6088) Socket#shutdownOutput in ServerImpl lead UnsupportedOperationException on SSLSocket
Evgenii Zhuravlev created IGNITE-6088: - Summary: Socket#shutdownOutput in ServerImpl lead UnsupportedOperationException on SSLSocket Key: IGNITE-6088 URL: https://issues.apache.org/jira/browse/IGNITE-6088 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Evgenii Zhuravlev Assignee: Evgenii Zhuravlev Fix For: 2.2 UnsupportedOperationException: The method shutdownOutput() is not supported in SSLSocket -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6053) IgniteCache.clear clears local cache with same names on all server nodes
Evgenii Zhuravlev created IGNITE-6053: - Summary: IgniteCache.clear clears local cache with same names on all server nodes Key: IGNITE-6053 URL: https://issues.apache.org/jira/browse/IGNITE-6053 Project: Ignite Issue Type: Bug Affects Versions: 1.7 Reporter: Evgenii Zhuravlev Fix For: 2.2 Clear on LOCAL cache should clear the only cache on the current node, not on all nodes, that have local caches with same names. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5985) WebConsole: add generation of keyFields for queryEntity for multiple primary key
Evgenii Zhuravlev created IGNITE-5985: - Summary: WebConsole: add generation of keyFields for queryEntity for multiple primary key Key: IGNITE-5985 URL: https://issues.apache.org/jira/browse/IGNITE-5985 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Assignee: Alexey Kuznetsov -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5922) Improve collisionSpi doc - ParallelJobsNumber should be less than PublicThreadPoolSize
Evgenii Zhuravlev created IGNITE-5922: - Summary: Improve collisionSpi doc - ParallelJobsNumber should be less than PublicThreadPoolSize Key: IGNITE-5922 URL: https://issues.apache.org/jira/browse/IGNITE-5922 Project: Ignite Issue Type: Improvement Components: documentation Reporter: Evgenii Zhuravlev Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5867) Web console: Add parameter for adding primary key columns to generated POJO class
Evgenii Zhuravlev created IGNITE-5867: - Summary: Web console: Add parameter for adding primary key columns to generated POJO class Key: IGNITE-5867 URL: https://issues.apache.org/jira/browse/IGNITE-5867 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5860) Client disconnects if server it is connected to goes unresponsive
Evgenii Zhuravlev created IGNITE-5860: - Summary: Client disconnects if server it is connected to goes unresponsive Key: IGNITE-5860 URL: https://issues.apache.org/jira/browse/IGNITE-5860 Project: Ignite Issue Type: Bug Affects Versions: 1.7 Reporter: Evgenii Zhuravlev Fix For: 2.2 Scenario is the following: # Start at least two server nodes. # Start a client node. # Detect server node client is connected to in discovery SPI. # Suspend that server (^Z in terminal or 'kill -SIGSTOP '). # It's expected that client will drop connection with this server and connect to another one. # However, a client gets dropped from topology and disconnects. A client should reconnect cluster before the timeout and without EVT_CLIENT_NODE_RECONNECTED event. In ClientImpl.Reconnector in joinTopology method it gets all addresses from discoverySpi and addresses of the server that was suspended on top of this list. Suggested solution: Move addresses of the suspended server to the end of the list for the join. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5814) Service deploy fails with NPE if it implements ExecutorService interface
Evgenii Zhuravlev created IGNITE-5814: - Summary: Service deploy fails with NPE if it implements ExecutorService interface Key: IGNITE-5814 URL: https://issues.apache.org/jira/browse/IGNITE-5814 Project: Ignite Issue Type: Bug Affects Versions: 1.9 Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5789) After client reconnects to server if server was restarted, client doesn't create caches defined in config file
Evgenii Zhuravlev created IGNITE-5789: - Summary: After client reconnects to server if server was restarted, client doesn't create caches defined in config file Key: IGNITE-5789 URL: https://issues.apache.org/jira/browse/IGNITE-5789 Project: Ignite Issue Type: Bug Affects Versions: 2.0 Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5778) Update JobMetrics on each job add/start/finish methods and add possibility to turn out JobMetrics and
Evgenii Zhuravlev created IGNITE-5778: - Summary: Update JobMetrics on each job add/start/finish methods and add possibility to turn out JobMetrics and Key: IGNITE-5778 URL: https://issues.apache.org/jira/browse/IGNITE-5778 Project: Ignite Issue Type: Improvement Affects Versions: 1.9 Reporter: Evgenii Zhuravlev Fix For: 2.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5776) Add option to turn out filter reachable addresses in TcpCommunicationSpi
Evgenii Zhuravlev created IGNITE-5776: - Summary: Add option to turn out filter reachable addresses in TcpCommunicationSpi Key: IGNITE-5776 URL: https://issues.apache.org/jira/browse/IGNITE-5776 Project: Ignite Issue Type: Improvement Reporter: Evgenii Zhuravlev Assignee: Evgenii Zhuravlev Fix For: 2.2 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5775) Compute runs one job in MetricsUpdateFrequency per thread after all jobs was submitted(as onCollision is not invokes)
Evgenii Zhuravlev created IGNITE-5775: - Summary: Compute runs one job in MetricsUpdateFrequency per thread after all jobs was submitted(as onCollision is not invokes) Key: IGNITE-5775 URL: https://issues.apache.org/jira/browse/IGNITE-5775 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5751) In TcpCommunicationSpi.createTcpClient U.filterReachable waits all addresses to check if they are reachable
Evgenii Zhuravlev created IGNITE-5751: - Summary: In TcpCommunicationSpi.createTcpClient U.filterReachable waits all addresses to check if they are reachable Key: IGNITE-5751 URL: https://issues.apache.org/jira/browse/IGNITE-5751 Project: Ignite Issue Type: Bug Affects Versions: 1.9 Reporter: Evgenii Zhuravlev Priority: Critical In TcpCommunicationSpi.createTcpClient replace U.filterReachable with filtering first reachable address -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5731) Wrong metrics calculation in ClusterMetricsSnapshot
Evgenii Zhuravlev created IGNITE-5731: - Summary: Wrong metrics calculation in ClusterMetricsSnapshot Key: IGNITE-5731 URL: https://issues.apache.org/jira/browse/IGNITE-5731 Project: Ignite Issue Type: Bug Affects Versions: 1.6 Reporter: Evgenii Zhuravlev Priority: Minor Error in ClusterMetricsSnapshot constructor: curWaitingJobs += m.getCurrentJobWaitTime(); avgWaitingJobs += m.getCurrentWaitingJobs(); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-5700) Port range defines in addresses should override TcpDiscoverySpi.localPortRange
Evgenii Zhuravlev created IGNITE-5700:
-
Summary: Port range defines in addresses should override
TcpDiscoverySpi.localPortRange
Key: IGNITE-5700
URL: https://issues.apache.org/jira/browse/IGNITE-5700
Project: Ignite
Issue Type: Bug
Affects Versions: 2.0
Reporter: Evgenii Zhuravlev
Priority: Minor
If addresses were configured with
{code:java}
127.0.0.1:47500..47502
{code}
with default localPortRange(100) it's possible for node to bind on 47503 port.
If localPortRange was set to 0, node can't join to 47501 port.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5663) ODBC: Few consecutive inserts lead to exception
Evgenii Zhuravlev created IGNITE-5663:
-
Summary: ODBC: Few consecutive inserts lead to exception
Key: IGNITE-5663
URL: https://issues.apache.org/jira/browse/IGNITE-5663
Project: Ignite
Issue Type: Bug
Components: odbc
Affects Versions: 1.8
Reporter: Evgenii Zhuravlev
Assignee: Igor Sapego
Exception: ('HY010', '[HY010] Query is not prepared. (0) (SQLExecDirectW)')
Reproducer in python:
{code:java}
import pyodbc
cnxn = pyodbc.connect(DRIVER='{Apache Ignite}',
ADDRESS='localhost:10800',CACHE="Person", autocommit=True)
cursor = cnxn.cursor()
select_string= "INSERT INTO Person(_key, id, firstName, lastName, salary)
VALUES (?, ? , 'abcd', 'dhsagd', 1000)"
id_list = (1,1)
id_list2 = (2,2)
cursor.execute(select_string, id_list)
cursor.execute(select_string, id_list2)
{code}
Also, the same behavior with executemany.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5597) Wrong javadoc in Affinity and AffinityFunction for REPLICATED cache
Evgenii Zhuravlev created IGNITE-5597:
-
Summary: Wrong javadoc in Affinity and AffinityFunction for
REPLICATED cache
Key: IGNITE-5597
URL: https://issues.apache.org/jira/browse/IGNITE-5597
Project: Ignite
Issue Type: Bug
Affects Versions: 1.7
Reporter: Evgenii Zhuravlev
RendezvoudAffinityFunction.getPartitions() Javadoc says:
{code:java}
* Note that for fully replicated caches this method should always
* return {@code 1}.
{code}
but it's not true, it works the same as PARTITIONED cache.
Affinity.mapKeyToNode(K key) javadoc says:
{code:java}
*
* For fully replicated caches first node ID returned by {@link
AffinityFunction}
* is returned.
*
* For partitioned caches, primary node for the given key is
returned.
{code}
it looks confusing, while REPLICATED cache has primary nodes for keys as
PRATITIONED.
Also,
{code:java}
* Provides affinity information to detect which node is primary and which nodes
are
* backups for a partitioned cache.
{code}
Affinity matter for REPLICATED cache too.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-5369) Add possibility to generate alias for primary key in WebConsole
Evgenii Zhuravlev created IGNITE-5369: - Summary: Add possibility to generate alias for primary key in WebConsole Key: IGNITE-5369 URL: https://issues.apache.org/jira/browse/IGNITE-5369 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Assignee: Alexey Kuznetsov Add field with alias name for primary key, that wiil be used in QueryEntity.setKeyFieldName -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5299) Don't set IgniteLock as broken if lock is failoverSafe
Evgenii Zhuravlev created IGNITE-5299: - Summary: Don't set IgniteLock as broken if lock is failoverSafe Key: IGNITE-5299 URL: https://issues.apache.org/jira/browse/IGNITE-5299 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev It's unnecessary to set isBroken flag to IgniteLock when failoverSafe=true, because it's only used in case when failoverSafe=false -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5232) GridDhtPartitionDemander.requestPartitions invokes sendMessages consequently, which lead to significant increase of node start time on large clusters with ssl
Evgenii Zhuravlev created IGNITE-5232: - Summary: GridDhtPartitionDemander.requestPartitions invokes sendMessages consequently, which lead to significant increase of node start time on large clusters with ssl Key: IGNITE-5232 URL: https://issues.apache.org/jira/browse/IGNITE-5232 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Fix For: 2.1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-5118) Table with name Object lead to compilation error in code generated by webconsole
Evgenii Zhuravlev created IGNITE-5118: - Summary: Table with name Object lead to compilation error in code generated by webconsole Key: IGNITE-5118 URL: https://issues.apache.org/jira/browse/IGNITE-5118 Project: Ignite Issue Type: Bug Affects Versions: 1.7 Reporter: Evgenii Zhuravlev Assignee: Alexey Kuznetsov -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4925) IgniteCacheEntryListenerEagerTtlDisabledTest.testSynchronousEventsObjectKeyValue test fails while invoking from IgniteBinaryCacheTestSuite
Evgenii Zhuravlev created IGNITE-4925: - Summary: IgniteCacheEntryListenerEagerTtlDisabledTest.testSynchronousEventsObjectKeyValue test fails while invoking from IgniteBinaryCacheTestSuite Key: IGNITE-4925 URL: https://issues.apache.org/jira/browse/IGNITE-4925 Project: Ignite Issue Type: Bug Affects Versions: 2.0 Reporter: Evgenii Zhuravlev Assignee: Evgenii Zhuravlev Fix For: 2.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (IGNITE-4869) Unnecessary benchmarcs for legacy minary identity
Evgenii Zhuravlev created IGNITE-4869: - Summary: Unnecessary benchmarcs for legacy minary identity Key: IGNITE-4869 URL: https://issues.apache.org/jira/browse/IGNITE-4869 Project: Ignite Issue Type: Bug Reporter: Evgenii Zhuravlev Assignee: Evgenii Zhuravlev Priority: Critical Fix For: 2.0 IgniteLegacyBinaryIdentityPutBenchmark & IgniteLegacyBinaryIdentityGetBenchmark isn't needed after removing BinaryObjectBuilder.hashCode(int) method -- This message was sent by Atlassian JIRA (v6.3.15#6346)
