[jira] [Created] (IGNITE-7168) Web Console: Cleanup webAgentDownloadVisibleStates
Alexey Kuznetsov created IGNITE-7168: Summary: Web Console: Cleanup webAgentDownloadVisibleStates Key: IGNITE-7168 URL: https://issues.apache.org/jira/browse/IGNITE-7168 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Alexey Kuznetsov Assignee: Ilya Borisov Fix For: 2.4 We moved "Agent download" to footer. Lets cleanup unused code шт header see "connectedClustersUnvisibleStates" in app\components\web-console-header. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] ignite pull request #3201: IGNITE-7160 Ignore messages from not alive and fa...
GitHub user akuramshingg opened a pull request: https://github.com/apache/ignite/pull/3201 IGNITE-7160 Ignore messages from not alive and failed nodes. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7160 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3201.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3201 commit a4dd068ab27d864f159d45e4b963215b332b0fac Author: Alexandr Kuramshin Date: 2017-12-12T04:03:20Z IGNITE-7160 Ignore messages from not alive and failed nodes. Add TcpDiscoverySplitTest. commit b8c08ed35262b7b2eaff4557e267338b8803d4dd Author: Alexandr Kuramshin Date: 2017-12-12T04:04:58Z IGNITE-7160 Ignore messages from not alive and failed nodes. Fix flaky and mute failing tests. commit 3f2cdeca44c4d1979f4762a6c67979ceb51e0269 Author: Alexandr Kuramshin Date: 2017-12-12T04:24:55Z IGNITE-7160 Ignore messages from not alive and failed nodes. SocketReader refactoring. ---
[GitHub] ignite pull request #3151: IGNITE-7055: Fix text query to work with a partic...
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3151 ---
Re: Suppressing "development" warning
I actually like the new WARNING_DEV_ONLY category for logging. If we provide it in the default logger configuration, then users will not have to do anything extra unless they want to change it. Moreover, if it is a category, then it can be turned on and off using standard logger configuration. D. On Mon, Dec 11, 2017 at 3:28 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Igniters, > > We have bunch of warnings in the product which are useful only during > development. One of the examples of is "Class ... cannot be serialized > using BinaryMarshaller because it either implements Externalizable ...' > warning - it is very useful when one is writing code as it warns about > possible mistakes and suggest how to fix them, but once implementation is > done, it is meaningless. Moreover, in production environments all warnings > and errors are often automatically monitored, so this introduces an issue > of false positive alerts generated by this kind of warnings. > > I see two possible solutions for this: > - Add 'devOnly' flag to IgniteLogger#warning method and ignore them if > special system property is set. > - Introduce special logger category for such warnings so that user can > control if they are logged or not. > > I think my vote is for the first option as it's more straightforward and > doesn't require any additional configuration from a user. > > Thoughts? > > -Val >
Suppressing "development" warning
Igniters, We have bunch of warnings in the product which are useful only during development. One of the examples of is "Class ... cannot be serialized using BinaryMarshaller because it either implements Externalizable ...' warning - it is very useful when one is writing code as it warns about possible mistakes and suggest how to fix them, but once implementation is done, it is meaningless. Moreover, in production environments all warnings and errors are often automatically monitored, so this introduces an issue of false positive alerts generated by this kind of warnings. I see two possible solutions for this: - Add 'devOnly' flag to IgniteLogger#warning method and ignore them if special system property is set. - Introduce special logger category for such warnings so that user can control if they are logged or not. I think my vote is for the first option as it's more straightforward and doesn't require any additional configuration from a user. Thoughts? -Val
[jira] [Created] (IGNITE-7167) Optimize 'select count(*) from Table'
Valentin Kulichenko created IGNITE-7167:
---
Summary: Optimize 'select count(*) from Table'
Key: IGNITE-7167
URL: https://issues.apache.org/jira/browse/IGNITE-7167
Project: Ignite
Issue Type: Improvement
Components: sql
Affects Versions: 2.3
Reporter: Valentin Kulichenko
Currently query like {{select count(*) from Table}} effectively scans the cache
and take a lot of time for large datasets. Probably makes sense to optimize it
to use {{IgniteCache#size}} directly when possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] ignite pull request #3200: Ignite 6341 & 7017: test PR
GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3200 Ignite 6341 & 7017: test PR You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6341-7017 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3200.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3200 commit 3edcf672d9b15cd46cf195326c4221be64c6374a Author: dpavlov Date: 2017-12-05T09:27:22Z IGNITE-7017: Archiver disabled WAL mode in case folders are equal commit b0ba50b3000298060666961d091d64392881ce12 Author: dpavlov Date: 2017-12-05T13:16:44Z IGNITE-7017: Archiver disabled by default: temp commit for benchmarking commit 172e86185d8cd709bc2a9c3c42fd3b07d3666c20 Author: dpavlov Date: 2017-12-05T14:39:46Z IGNITE-7017: Archiver disabled by default: code commenting commit 49275830380d79e617b83d0042e2f370fd0b68c3 Author: dpavlov Date: 2017-12-06T11:35:18Z IGNITE-6341: JNA based-library research started commit 6035542c395cc7490e15a60d3436989c44d8421b Author: dpavlov Date: 2017-12-06T12:14:11Z IGNITE-6341: missed library returned commit 308e88a1f8cd1a92911449c8cb4bcaef29e76076 Author: dpavlov Date: 2017-12-06T13:06:07Z javadoc fix commit c20f2b4de713a340e00cc0a94a9a4dabb15324e4 Author: dpavlov Date: 2017-12-06T14:40:21Z IGNITE-7017: Format file for mode without archiver commit f133b94af8c83876f1251043048d732b8bab4f19 Author: dspavlov Date: 2017-12-06T15:21:23Z IGNITE-7017: page store tests with 3rd party align library: only heap buffers are applicable commit eecb7cbf9f3e506297bab19b97fa683da04069d9 Author: dspavlov Date: 2017-12-06T17:13:29Z IGNITE-7017: file written using Direct IO commit bfc8513bbdcce4fc91120d35660d6c86865cd87a Author: dspavlov Date: 2017-12-06T18:26:26Z IGNITE-7017: file written using Direct IO, simple test for existing page store. commit 5f351a4936dc7e59c136aa9885956b73a090eb4f Author: dspavlov Date: 2017-12-06T18:31:43Z IGNITE-7017: Headers commit 6f8c6498745894da3355e1d7be248829623a7219 Author: dspavlov Date: 2017-12-07T10:54:36Z IGNITE-6341: direct IO used to write page store header commit 68412929827ff44fd8a366fabac263e83f9022b5 Author: dpavlov Date: 2017-12-07T12:18:36Z IGNITE-7017: Format file for mode without archiver in all modes commit 2ff7505161583eefa521ec4e6fa06bb741d772e5 Author: dpavlov Date: 2017-12-07T13:10:33Z IGNITE-7017: resize file with write 1 byte to the end of segment commit 53576384a9d87d3cdca794029654cebc7236ff52 Author: dspavlov Date: 2017-12-07T13:33:55Z IGNITE-6341: direct IO used to read page store header commit 5e334f535913a195cb805f8637d6d37eac088106 Author: dspavlov Date: 2017-12-07T13:48:02Z IGNITE-6341: direct IO used to read-write pages commit b57f47609641b2fe98a430c4609b08cb3285ce2b Author: dspavlov Date: 2017-12-07T14:35:27Z IGNITE-6341: direct with aligned buffers for checkpointer commit 477f321b497ad02b147bb3db0c3004cc10927c99 Author: dspavlov Date: 2017-12-07T17:07:32Z IGNITE-6341: caching one-page sized buffers in TLB in IO factory commit 5e0bbe83bc4b38356ccf8b67721f444f5cf83c00 Author: dpavlov Date: 2017-12-07T18:02:01Z IGNITE-6341: Startup on non linux OS commit 14d25df8f3d70977dabbf4c5cb11bf3629918b5c Author: dspavlov Date: 2017-12-07T19:21:41Z IGNITE-6341: Page size determining using path and linux page size, backup factory used, logging commit 5d42b485a10c214fbdd65bba43d96dcdc3a442d6 Author: dpavlov Date: 2017-12-07T19:27:50Z IGNITE-6341: Test startup fix commit 889831efd6ac3b7c4880fa89d139bb21e218797b Author: dspavlov Date: 2017-12-08T09:34:58Z IGNITE-6341: Linux version check commit 4c1d234737a1e5e6b08f2efe7d66868b45cd9412 Author: dspavlov Date: 2017-12-08T10:25:01Z IGNITE-6341: NativeIO lib is implemented as plugin commit db14234c7bc1e865caba9a681cf8a2f1b571295f Author: dspavlov Date: 2017-12-08T10:25:20Z IGNITE-6341: NativeIO lib is implemented as plugin commit fd9b085c7e37bb7afb5e0cbbc2e25805e5c07655 Author: dspavlov Date: 2017-12-08T11:13:57Z IGNITE-6341: NativeIO lib is implemented as plugin: test passed, monitoring active threads commit 5fc44aa55b194a393f126e86693ccc30b89b8919 Author: dpavlov Date: 2017-12-08T15:34:12Z IGNITE-6341: Code cleanup, code commenting. commit 3c1655b68790bdf68e401c90ba0fec77ba08612e Author: dpavlov Date: 2017-12-08T15:39:01Z IGNITE-6341: Code cleanup, code commenting. commit df0666068e46b2fbc1364369842d5b82c36c83d8 Author: dpavlov Date: 2017-12-08T17:02:19Z IGNITE-6341: Code cleanup, code commenting. commit 4d05f3cb2538037fc76a3cab8f76a7e1726a817b Author: dspavlov Date: 2017-12-08T17:38:16Z IGNITE-6341: Da
[GitHub] ignite pull request #3199: IGNITE-6740: Replaced direct sun.nio.ch.DirectBuf...
GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3199 IGNITE-6740: Replaced direct sun.nio.ch.DirectBuffer.address() call with reflective one You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6740 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3199.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3199 commit 14f5e8ed3ada76464740e5a7d9def469a60e04db Author: Andrey Kuznetsov Date: 2017-12-11T17:47:50Z IGNITE-6740: Replaced direct sun.nio.ch.DirectBuffer.address() call with reflective one. ---
[GitHub] ignite pull request #3117: IGNITE-6880: KNN Regression and Classification
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3117 ---
[jira] [Created] (IGNITE-7166) SQL join with partition and replicated caches fails if number of partitions is too low.
Alexei Scherbakov created IGNITE-7166:
-
Summary: SQL join with partition and replicated caches fails if
number of partitions is too low.
Key: IGNITE-7166
URL: https://issues.apache.org/jira/browse/IGNITE-7166
Project: Ignite
Issue Type: Bug
Affects Versions: 2.3
Reporter: Alexei Scherbakov
Fix For: 2.4
Reproducer:
{noformat}
/*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with
* this work for additional information regarding copyright ownership.
* The ASF licenses this file to You under the Apache License, Version 2.0
* (the "License"); you may not use this file except in compliance with
* the License. You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*/
package org.apache.ignite.internal.processors.cache.distributed.replicated;
import java.util.List;
import org.apache.ignite.Ignite;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cache.query.FieldsQueryCursor;
import org.apache.ignite.cache.query.SqlFieldsQuery;
import org.apache.ignite.cache.query.annotations.QuerySqlField;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheMode.PARTITIONED;
import static org.apache.ignite.cache.CacheMode.REPLICATED;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
/**
* Tests non collocated join with replicated cache.
*/
public class IgniteCacheReplicatedJoinSelfTest extends GridCommonAbstractTest {
/** */
public static final String REP_CACHE_NAME = "repCache";
/** */
public static final String PART_CACHE_NAME = "partCache";
/** */
public static final int REP_CNT = 3;
/** */
public static final int PART_CNT = 10_000;
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
final IgniteConfiguration cfg =
super.getConfiguration(igniteInstanceName);
cfg.setClientMode("client".equals(igniteInstanceName));
final CacheConfiguration ccfg1 = new
CacheConfiguration(PART_CACHE_NAME);
ccfg1.setCacheMode(PARTITIONED);
ccfg1.setAtomicityMode(TRANSACTIONAL);
ccfg1.setWriteSynchronizationMode(FULL_SYNC);
ccfg1.setIndexedTypes(Integer.class, PartValue.class);
final CacheConfiguration ccfg2 = new CacheConfiguration(REP_CACHE_NAME);
ccfg2.setAffinity(new RendezvousAffinityFunction(false, REP_CNT));
ccfg2.setCacheMode(REPLICATED);
ccfg2.setAtomicityMode(TRANSACTIONAL);
ccfg2.setWriteSynchronizationMode(FULL_SYNC);
ccfg2.setIndexedTypes(Integer.class, RepValue.class);
cfg.setCacheConfiguration(ccfg1, ccfg2);
return cfg;
}
/**
*
* @throws Exception
*/
public void testJoinNonCollocated() throws Exception {
startGridsMultiThreaded(3);
final Ignite client = startGrid("client");
for (int i = 0; i < REP_CNT; i++)
client.cache(REP_CACHE_NAME).put(i, new RepValue(i, "rep" + i));
for (int i = 0; i < PART_CNT; i++)
client.cache(PART_CACHE_NAME).put(i, new PartValue(i, "part" + i,
((i + 1) % REP_CNT)));
final FieldsQueryCursor> qry = client.cache(PART_CACHE_NAME).
query(new SqlFieldsQuery("select PartValue._VAL, r._VAL from
PartValue, \"repCache\".RepValue as r where PartValue.repId=r.id"));
final List> all = qry.getAll();
assertEquals(10_000, all.size());
for (List objects : all) {
final PartValue pv = (PartValue)objects.get(0);
final RepValue rv = (RepValue)objects.get(1);
assertNotNull(rv);
assertEquals(rv.getId(), pv.getRepId());
}
}
/** */
public static class PartValue {
/** Id. */
@QuerySqlField
private int id;
/** Name. */
@QuerySqlField
private String name;
/** Rep id. */
@QuerySqlField
private int repId;
/**
* @param id Id.
* @param name Name.
* @param repId Rep id.
*/
public PartValue(int id, String name, int repId) {
t
[GitHub] ignite pull request #3198: Ignite 6669 2.1 master
GitHub user sk0x50 opened a pull request: https://github.com/apache/ignite/pull/3198 Ignite 6669 2.1 master You can merge this pull request into a Git repository by running: $ git pull https://github.com/sk0x50/ignite ignite-6669-2.1-master Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3198.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3198 commit 5b70793c9d633ec2179a22f842aead5880caa55d Author: Pavel Tupitsyn Date: 2017-09-12T08:29:15Z IGNITE-6253 .NET: Use DocFX for API documentation commit 8470f32a546a5eacaa9c905735dda7a307713c8d Author: Alexander Paschenko Date: 2017-09-12T08:40:47Z IGNITE-5703: SQL: Added WRITE_SYNCHRONIZATION_MODE parameter to CREATE TABLE command. This closes #2591. commit e17ad23b89a016fe30cbac29266d10c65b6ede96 Author: devozerov Date: 2017-09-12T08:41:56Z Merge remote-tracking branch 'upstream/ignite-2.1.5' into ignite-2.1.5 commit b06c89c7c9c2ddf65ad7c9b7877e7a1e1c55669a Author: Igor Sapego Date: 2017-09-12T11:44:07Z IGNITE-6151: Impemented getting and setting of the SQL_ATTR_CONNECTION_DEAD (cherry picked from commit 0bc1d84) commit 9489e9a59ce6eb9aa63cf84dc40269029794ca3e Author: Igor Sapego Date: 2017-09-12T13:10:51Z IGNITE-6151: Review fixes (cherry picked from commit 8c23805) commit 726a35208c48f613ec43f17139a2ab48c11a0b94 Author: Sergey Kalashnikov Date: 2017-09-12T13:53:50Z IGNITE-5648: SQL: Added support for NOT NULL constraint. This closes #2341. commit 4194aafd2928905176a93892d808793451f399ee Author: devozerov Date: 2017-09-12T14:33:23Z Added more memory to DynamicColumnsAbstractTest. commit 4d305e19ab790a196337812723d3297e2d152d84 Author: Pavel Tupitsyn Date: 2017-09-12T14:41:38Z IGNITE-6354 .NET: Fix DataStreamer with complex object graphs Cherry-picked from commit 67d716f00806c8d69f8339b090e0ddd877b225e3 commit c8c20737ef260b401b53aeb57a709bdc4fdc2e88 Author: vsisko Date: 2017-09-13T06:39:28Z IGNITE-6363 Added refresh icon. (cherry picked from commit cc3ab69) commit ba72515adc50f6132795abcd49ef7e695f06d8a2 Author: Pavel Tupitsyn Date: 2017-09-13T09:17:45Z IGNITE-6081 .NET: Fix PutAll for dependent objects Cherry-pick remaining changes commit 98f176612ceff66b7530e720d73c6bf0b1b61962 Author: Pavel Tupitsyn Date: 2017-09-13T09:50:49Z IGNITE-6121 .NET: Propagate SqlFieldsQuery.lazy property commit d1a79b323dd3a1689a23d35644e6e3b27cd26f3f Author: Vasiliy Sisko Date: 2017-09-13T10:09:03Z IGNITE-6229 Fixes in code generation. (cherry picked from commit d753e90) commit e23749078ecfd46c4172b8449afeb415902c607c Author: Alexey Goncharuk Date: 2017-09-13T10:42:31Z IGNITE-6356 - Fixed overflow when using number of partitions greater than Short.MAX_VALUE commit a32b342289dca38668f6a847171b6a2bd38ad40d Author: devozerov Date: 2017-09-13T10:46:13Z IGNITE-5896: Preparing base client request for integration with thin client. commit 82d8d9fec9384127e75bfa6108445043b1392352 Author: Pavel Tupitsyn Date: 2017-09-13T10:56:18Z IGNITE-5896: Base thin client requests. commit 761cfcbd4357cb7a18011cdb0756f13dd3866250 Author: Pavel Tupitsyn Date: 2017-09-13T11:12:41Z IGNITE-5896: Thin client: added base client cache get/put requests. commit c6478c4ba3974cf20387c658d245ef30155d4164 Author: Pavel Tupitsyn Date: 2017-09-13T11:28:38Z IGNITE-5896: Thin client: base server-side infrastructure. commit 960b6d9b09052fbd2eca9605e3a81ef782f611e4 Author: Alexey Goncharuk Date: 2017-09-13T11:49:40Z Fixed compilation commit 21d709d82d143ea3e380bd0b6be5740d215e5d4e Author: anovikov Date: 2017-09-13T11:01:58Z IGNITE-6366 Improve web agent version check. (cherry picked from commit 40a9cc1) commit ff58c61e5652b7335f46b10ebf0f88ecd4e32a10 Author: Pavel Tupitsyn Date: 2017-07-25T12:15:43Z IGNITE-5770 Refactor PlatformProcessor to PlatformTarget mechanism This closes #2336 (cherry picked from commit bdc9e4b) commit b2bb2a3c98434cfce5693bd1927be17e3d785e9a Author: Igor Sapego Date: 2017-09-13T13:21:56Z IGNITE-6330: Implemented closing of ODBC and JDBC cursors on disconnect (cherry picked from commit 28b5c11) commit 7761b4992f6c77e9b9fbfb08291d4b53a314067b Author: Ilya Lantukh Date: 2017-09-13T16:13:46Z ignite-5549 : Clear MvccManager.pending queue after AsyncOp.op(...). - Fixes #2626. Signed-off-by: Alexey Goncharuk commit fbbc8cbb0831df3d8c3dd4ac946423dca6ecc650 Author: Ilya Lantukh Date: 2017-09-14T07:44:29Z IGNITE-6340 Fixed incorrect client cache creation on server side. Fixes #2635 commit 5de852b929fda331dbf511747f44bbaed0c23152 Author: Igor Sapego Date: 2017-09-13T15:12:13Z IGNITE-6330: Merge-related bugfix. commi
[GitHub] ignite pull request #2703: PR to add branch to TC
Github user alexzaitzev closed the pull request at: https://github.com/apache/ignite/pull/2703 ---
[jira] [Created] (IGNITE-7165) Re-balancing is cancelled if client node joins
Mikhail Cherkasov created IGNITE-7165: - Summary: Re-balancing is cancelled if client node joins Key: IGNITE-7165 URL: https://issues.apache.org/jira/browse/IGNITE-7165 Project: Ignite Issue Type: Bug Reporter: Mikhail Cherkasov Assignee: Anton Vinogradov Priority: Critical Re-balancing is canceled if client node joins. Re-balancing can take hours and each time when client node joins it starts again: [15:10:05,700][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] Added new node to topology: TcpDiscoveryNode [id=979cf868-1c37-424a-9ad1-12db501f32ef, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 172.31.16.213], sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /172.31.16.213:0], discPort=0, order=36, intOrder=24, lastExchangeTime=1512907805688, loc=false, ver=2.3.1#20171129-sha1:4b1ec0fe, isClient=true] [15:10:05,701][INFO][disco-event-worker-#61%statement_grid%][GridDiscoveryManager] Topology snapshot [ver=36, servers=7, clients=5, CPUs=128, heap=160.0GB] [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Started exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], crd=false, evt=NODE_JOINED, evtNode=979cf868-1c37-424a-9ad1-12db501f32ef, customEvt=null, allowMerge=true] [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionsExchangeFuture] Finish exchange future [startVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], resVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], err=null] [15:10:05,702][INFO][exchange-worker-#62%statement_grid%][time] Finished exchange init [topVer=AffinityTopologyVersion [topVer=36, minorTopVer=0], crd=false] [15:10:05,703][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion [topVer=36, minorTopVer=0], evt=NODE_JOINED, node=979cf868-1c37-424a-9ad1-12db501f32ef] [15:10:08,706][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] Cancelled rebalancing from all nodes [topology=AffinityTopologyVersion [topVer=35, minorTopVer=0]] [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] Rebalancing scheduled [order=[statementp]] [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridCachePartitionExchangeManager] Rebalancing started [top=null, evt=NODE_JOINED, node=a8be3c14-9add-48c3-b099-3fd304cfdbf4] [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] Starting rebalancing [mode=ASYNC, fromNode=2f6bde48-ffb5-4815-bd32-df4e57dc13e0, partitionsCount=18, topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], updateSeq=-1754630006] [15:10:08,707][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] Starting rebalancing [mode=ASYNC, fromNode=35d01141-4dce-47dd-adf6-a4f3b2bb9da9, partitionsCount=15, topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], updateSeq=-1754630006] [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] Starting rebalancing [mode=ASYNC, fromNode=b3a8be53-e61f-4023-a906-a265923837ba, partitionsCount=15, topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], updateSeq=-1754630006] [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] Starting rebalancing [mode=ASYNC, fromNode=f825cb4e-7dcc-405f-a40d-c1dc1a3ade5a, partitionsCount=12, topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], updateSeq=-1754630006] [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] Starting rebalancing [mode=ASYNC, fromNode=4ae1db91-8b88-4180-a84b-127a303959e9, partitionsCount=11, topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], updateSeq=-1754630006] [15:10:08,708][INFO][exchange-worker-#62%statement_grid%][GridDhtPartitionDemander] Starting rebalancing [mode=ASYNC, fromNode=7c286481-7638-49e4-8c68-fa6aa65d8b76, partitionsCount=18, topology=AffinityTopologyVersion [topVer=36, minorTopVer=0], updateSeq=-1754630006] so in clusters with a big amount of data and the frequent client left/join events this means that a new server will never receive its partitions. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] ignite pull request #3189: Ignite 7053
Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3189 ---
[jira] [Created] (IGNITE-7164) SQL TX: Locking protocol for complex cases
Igor Seliverstov created IGNITE-7164: Summary: SQL TX: Locking protocol for complex cases Key: IGNITE-7164 URL: https://issues.apache.org/jira/browse/IGNITE-7164 Project: Ignite Issue Type: Task Components: sql Reporter: Igor Seliverstov Currently several features are still unimplemented: # Implicit transactions # Optimistic transactions # Transactional SQL updates during rebalancing # Updates on backup nodes/Replicated caches support # Near caches support # TX restore # Remap on topology changes -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7163) Validate connection from a pre-previous node
Alexandr Kuramshin created IGNITE-7163: -- Summary: Validate connection from a pre-previous node Key: IGNITE-7163 URL: https://issues.apache.org/jira/browse/IGNITE-7163 Project: Ignite Issue Type: Sub-task Affects Versions: 2.3 Reporter: Alexandr Kuramshin Assignee: Alexandr Kuramshin If some pre-previous node connects to the local node with the previous node in the message's failed nodes collection additional steps should be done: # Connection with the previous node should be validated. # If a message from the previous node was not received a long time ago, the previous node should be considered as failed and the pre-previous node connection accepted. # If the previous node connection is alive then different scenarios possible ## Answer with a new result code causing the pre-previous node to try to reconnect to the previous node ## Break connection with the pre-previous node causing to continue the possible cluster split. ## Check connections with nodes after pre-previous node and delay decision by answering RES_WAIT to get more predictable split and stable topology. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7162) Control discovery messages processing time
Alexandr Kuramshin created IGNITE-7162: -- Summary: Control discovery messages processing time Key: IGNITE-7162 URL: https://issues.apache.org/jira/browse/IGNITE-7162 Project: Ignite Issue Type: Sub-task Components: general Affects Versions: 2.3 Reporter: Alexandr Kuramshin Assignee: Alexandr Kuramshin The majority of discovery message processing occurs in a single thread. If some message processing takes significant time it causes delaying of processing other messages and further undesirable effects on another protocols. Proposed to control processing time on the every node and total processing time of any given message. If processing takes significant time - log the warning. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] ignite pull request #3197: Ignite 6734
GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3197 Ignite 6734 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrey-kuznetsov/ignite ignite-6734 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3197.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3197 commit aff7c61f66ed0ba8de051f8ab037aa8f3076f167 Author: Andrey Kuznetsov Date: 2017-12-11T12:04:45Z IGNITE-6734: Switched language level to 8 for entire project. commit cac8bcc74fc2075a75a74c445757ccce9f86c4f2 Author: Andrey Kuznetsov Date: 2017-12-11T12:08:34Z IGNITE-6734: Replaced sun.misc.BASE64Encoder with standard Java 8 encoder. ---
[jira] [Created] (IGNITE-7161) Detect self-freeze on remote node related operations with timeout
Alexandr Kuramshin created IGNITE-7161:
--
Summary: Detect self-freeze on remote node related operations with
timeout
Key: IGNITE-7161
URL: https://issues.apache.org/jira/browse/IGNITE-7161
Project: Ignite
Issue Type: Sub-task
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin
After getting next timeout from
{{IgniteSpiOperationTimeoutHelper.nextTimeoutChunk()}} we starting a network
operation and expecting to end it at the specific timestamp (or near about).
We should take into account that some local thread freeze may be occurred. In
such situation a remote node should not be considered as failed and the local
network operation has to be retried.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (IGNITE-7160) Ignore messages from not alive and failed nodes
Alexandr Kuramshin created IGNITE-7160:
--
Summary: Ignore messages from not alive and failed nodes
Key: IGNITE-7160
URL: https://issues.apache.org/jira/browse/IGNITE-7160
Project: Ignite
Issue Type: Sub-task
Components: general
Affects Versions: 2.3
Reporter: Alexandr Kuramshin
Assignee: Alexandr Kuramshin
Current implementation of {{ServerImpl}} accepts and processes messages from
any other remote node even it was failed or removed from the ring.
Proposed to process only specific messages (which have to be processed in the
current node state). Some messages could be silently ignored, receiving other
undesirable messages causes the remote socket disconnect.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] ignite pull request #3196: IGNITE-7159 - Fix IgniteCacheAtomicExpiryPolicyWi...
GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/3196 IGNITE-7159 - Fix IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetR⦠â¦eadThrough You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7159 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3196.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3196 commit c190864356f56d7f0c73d405ba630bbdd5d88a26 Author: xmitya Date: 2017-12-11T11:11:40Z IGNITE-7159 - Fix IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough ---
[jira] [Created] (IGNITE-7159) Fix IGNITE-7086 fails IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough
Dmitry Karachentsev created IGNITE-7159: --- Summary: Fix IGNITE-7086 fails IgniteCacheAtomicExpiryPolicyWithStoreTest.testGetReadThrough Key: IGNITE-7159 URL: https://issues.apache.org/jira/browse/IGNITE-7159 Project: Ignite Issue Type: Bug Reporter: Dmitry Karachentsev -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-7158) TCP discovery improvement
Alexandr Kuramshin created IGNITE-7158: -- Summary: TCP discovery improvement Key: IGNITE-7158 URL: https://issues.apache.org/jira/browse/IGNITE-7158 Project: Ignite Issue Type: Improvement Components: general Affects Versions: 2.3 Reporter: Alexandr Kuramshin Assignee: Alexandr Kuramshin Current TCP discovery implementation has different drawbacks which should be fixed. See sub-tasks for details. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] ignite pull request #3195: JMX metrics implementation
GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3195 JMX metrics implementation You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-2.3-fix Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3195.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3195 commit d958974ff2c3b945f290b995e71b3362668d8acd Author: Aleksey Plekhanov Date: 2017-11-21T10:56:34Z IGNITE-6868 Implement new JMX metrics for TcpCommunicationSpi monitoring commit 601ac7e4f4df502cd76f0c62e168e604fa401288 Author: Aleksey Plekhanov Date: 2017-11-21T10:39:20Z IGNITE-6869 Implement new JMX metric for jobs monitoring commit d27fcd348b06d9de2871e11d8e45be0b03153995 Author: Pereslegin Pavel Date: 2017-11-24T12:35:02Z IGNITE-6867 Implement new JMX metrics for topology monitoring commit 898a3bd70ff428c903beee6ed2823d22b438f601 Author: Aleksey Plekhanov Date: 2017-11-24T11:44:07Z IGNITE-6870 Implement new JMX metric for cache topology validation monitoring commit 3bc502cfece7d003e767812cbd578f882e55c1d7 Author: Aleksey Plekhanov Date: 2017-11-30T10:14:18Z IGNITE-6871 Implement new JMX metrics for partitions map monitoring commit 73c9b4268f1f8d652d6bbe54b2ddd13f2ea01bb9 Author: Aleksey Plekhanov Date: 2017-11-23T13:54:01Z IGNITE-6985 Wrong value of RebalancingStartTime cache metric commit acf2ff5a126d6150052fca3296c9e7bf6eb323fb Author: Aleksey Plekhanov Date: 2017-12-08T14:13:54Z IGNITE-6867 Implement new JMX metrics for topology monitoring HotFix commit 4ee10ca51f8a792b5b54c9ed62798c80d8f4ea35 Author: Aleksey Plekhanov Date: 2017-12-08T14:17:06Z IGNITE-6868 Implement new JMX metrics for TcpCommunicationSpi monitoring HotFix commit fb1cab7e24ff75c16d852b608aecf5f78f6cd630 Author: Aleksey Plekhanov Date: 2017-12-08T14:22:18Z IGNITE-6871 Implement new JMX metrics for partitions map monitoring HotFix commit c019a9ea03c025f10a7dc0fa3bd403249ea55f89 Author: Aleksey Plekhanov Date: 2017-12-10T20:56:46Z Compatibility tests ---
[GitHub] ignite pull request #3194: IGNITE-7039: SQL: local query now pin affected pa...
GitHub user dolphin1414 opened a pull request: https://github.com/apache/ignite/pull/3194 IGNITE-7039: SQL: local query now pin affected partitions. Implemented partitions reservation for the local queries. Added a test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7039 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3194.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3194 commit 9a851a58ad5eb43f5b868d4a72013ce4a9beb395 Author: rkondakov Date: 2017-12-09T17:39:26Z IGNITE-7039: Partitions reservation for the local queries is implemented. commit dac1fc52cef92eae848966e85218da79092a48fa Author: rkondakov Date: 2017-12-11T09:52:04Z IGNITE-7039: Tests implemented. commit 769ac1a7f2d66677127cdbc1ea367ee873132220 Author: rkondakov Date: 2017-12-11T09:52:50Z Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ignite into ignite-7039 ---
[GitHub] ignite pull request #2434: IGNITE-6009: Fixed IgniteSemaphore test.
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2434 ---
[GitHub] ignite pull request #2877: IGNITE-1804: Test is not flaky anymore
Github user andrey-kuznetsov closed the pull request at: https://github.com/apache/ignite/pull/2877 ---
[GitHub] ignite pull request #2489: ignite-5714 thread id amended to data structure
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2489 ---
[GitHub] ignite pull request #2493: ignite-5714-1
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2493 ---
[GitHub] ignite pull request #2495: ignite-5714-3
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2495 ---
[GitHub] ignite pull request #2524: Ignite-5714 threadId removed from Near finish res...
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2524 ---
[GitHub] ignite pull request #2516: ignite-5714-5
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2516 ---
[GitHub] ignite pull request #2751: ignite-5714-8
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2751 ---
[GitHub] ignite pull request #2746: Ignite-5714-2
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2746 ---
[GitHub] ignite pull request #3079: Ignite incorrect state reconnect
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/3079 ---
[GitHub] ignite pull request #2788: ignite-5714 xid instead thread id in postLockWrit...
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2788 ---
[GitHub] ignite pull request #2759: ignite-5714-6
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2759 ---
[GitHub] ignite pull request #2768: ignite-5714 refactoring proposal for unused remot...
Github user voipp closed the pull request at: https://github.com/apache/ignite/pull/2768 ---
[GitHub] ignite pull request #2978: Ignite 5910
Github user SomeFire closed the pull request at: https://github.com/apache/ignite/pull/2978 ---
[GitHub] ignite pull request #2979: Ignite 5910 2
Github user SomeFire closed the pull request at: https://github.com/apache/ignite/pull/2979 ---
[GitHub] ignite pull request #3193: IGNITE-7157: Fixed deadlock when partition evicti...
GitHub user AMashenkov opened a pull request: https://github.com/apache/ignite/pull/3193 IGNITE-7157: Fixed deadlock when partition eviction run in different threads. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7157 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/3193.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #3193 commit cec30537cd08de42ae1be43f36a1fc80c1577b32 Author: Andrey V. Mashenkov Date: 2017-12-07T16:16:25Z IGNITE-7157: Fixed deadlock when partition eviction run in different threads. ---
[jira] [Created] (IGNITE-7157) Deadlock on partition eviction from multiple threads.
Andrew Mashenkov created IGNITE-7157: Summary: Deadlock on partition eviction from multiple threads. Key: IGNITE-7157 URL: https://issues.apache.org/jira/browse/IGNITE-7157 Project: Ignite Issue Type: Bug Components: cache Reporter: Andrew Mashenkov Fix For: 2.4 When node receive partition update message, it acquire partition and checkpoint locks in different order than asyncronous eviction. PFA thread dump. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
