[jira] [Created] (IGNITE-8996) Web console: Dropdown pupup menu is scrolled with page body on modal dialog.

[Vasiliy Sisko (JIRA)]

Vasiliy Sisko created IGNITE-8996:
-

 Summary: Web console: Dropdown pupup menu is scrolled with page 
body on modal dialog.
 Key: IGNITE-8996
 URL: https://issues.apache.org/jira/browse/IGNITE-8996
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 2.6
Reporter: Vasiliy Sisko
Assignee: Dmitriy Shabalin


# Open *Cluster* configuration of *Advanced* tab of *Configure* page.
 # Open *Import from database* dialog
 # On *Tables* step expand any dropdown
 # Try to scroll mouse on area instead of import dialog.

On scroll the dropdown popup is scrolled together with background content.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4354: IGNITE-8995 FailureHandler executed on error in S...

[dgladkikh]

GitHub user dgladkikh opened a pull request:

https://github.com/apache/ignite/pull/4354

IGNITE-8995 FailureHandler executed on error in ScanQuery's IgniteBiP…

…redicate.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-8995

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4354.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 #4354


commit 7d608e2c6e21b51d44f6f2c23dd3e9abd831d868
Author: dgladkikh 
Date:   2018-07-13T03:59:49Z

IGNITE-8995 FailureHandler executed on error in ScanQuery's 
IgniteBiPredicate.




---

[jira] [Created] (IGNITE-8995) FailureHandler executed on error in ScanQuery's IgniteBiPredicate

[Dmitriy Gladkikh (JIRA)]

Dmitriy Gladkikh created IGNITE-8995:


 Summary: FailureHandler executed on error in ScanQuery's 
IgniteBiPredicate
 Key: IGNITE-8995
 URL: https://issues.apache.org/jira/browse/IGNITE-8995
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.5
Reporter: Dmitriy Gladkikh


This code demonstrates this behavior:


{code:java}
import java.util.Collections;
import javax.cache.Cache;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
import org.apache.ignite.Ignition;
import org.apache.ignite.binary.BinaryObject;
import org.apache.ignite.cache.CacheAtomicityMode;
import org.apache.ignite.cache.CacheMode;
import org.apache.ignite.cache.query.QueryCursor;
import org.apache.ignite.cache.query.ScanQuery;
import org.apache.ignite.configuration.CacheConfiguration;
import org.apache.ignite.configuration.DataRegionConfiguration;
import org.apache.ignite.configuration.DataStorageConfiguration;
import org.apache.ignite.configuration.IgniteConfiguration;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;

/**
 * -ea -DIGNITE_QUIET=false
 */
public class ScanQueryIgniteBiPredicateWithError {
private static final String CACHE_NAME = "test_cache_name";

public static void main(String[] args) {
try (Ignite igniteServer = Ignition.start(getCfg("node_server", false));
 Ignite igniteClient = Ignition.start(getCfg("node_client", true)))
{
IgniteCache cache = 
igniteClient.cache(CACHE_NAME);

cache.put(1, 
igniteClient.binary().builder("test_type").setField("field_0", 
"field_0_val").build());

try (QueryCursor> cursor = 
cache.withKeepBinary().query(new ScanQuery<>(
new IgniteBiPredicate() {
@Override public boolean apply(Integer key, BinaryObject 
value) {
throw new AssertionError(); // Error.
//return value.field(null) != null; // Error.
//return true; // Ok.
}
})))
{
for (Cache.Entry entry : cursor)
// Without error in IgniteBiPredicate:
// Key = 1, Val = test_type [idHash=2024711353, 
hash=394028655, field_0=val_0]
System.out.printf("Key = %s, Val = %s%n", entry.getKey(), 
entry.getValue());
}
}
}

/**
 * @param instanceName Ignite instance name.
 * @param clientMode Client mode.
 * @return Ignite configuration.
 */
private static IgniteConfiguration getCfg(String instanceName, boolean 
clientMode) {
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();

ipFinder.setAddresses(Collections.singletonList("127.0.0.1:47500..47509"));

TcpDiscoverySpi tcpDiscoverySpi = new TcpDiscoverySpi();
tcpDiscoverySpi.setIpFinder(ipFinder);

DataRegionConfiguration dataRegionCfg = new DataRegionConfiguration();
dataRegionCfg.setPersistenceEnabled(true);

DataStorageConfiguration dataStorageCfg = new 
DataStorageConfiguration();
dataStorageCfg.setDefaultDataRegionConfiguration(dataRegionCfg);

CacheConfiguration ccfg = new 
CacheConfiguration(CACHE_NAME)
.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL)
.setCacheMode(CacheMode.PARTITIONED);

IgniteConfiguration cfg = new IgniteConfiguration();
cfg.setIgniteInstanceName(instanceName);
cfg.setDiscoverySpi(tcpDiscoverySpi);
cfg.setDataStorageConfiguration(dataStorageCfg);
cfg.setCacheConfiguration(ccfg);

if (!clientMode)
cfg.setAutoActivationEnabled(true);
else
cfg.setClientMode(true);

return cfg;
}
}
{code}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Cache 6 Suite Execution timeouts

[Dmitry Pavlov]

Suite is still sometimes timed out but now by
CacheExchangeMergeTest.testConcurrentStartServersAndClients.

чт, 24 мая 2018 г. в 16:24, Alexei Scherbakov :

> Hi, guys.
>
> Thanks for pointing this out.
>
> I'll look at this then I'll have available time.
>
> Possibly next week.
>
> Meanwhile I suggest not to use async rollbacks for transactions on near
> caches.
>
> чт, 24 мая 2018 г. в 14:09, Dmitry Pavlov :
>
>> Alexey? Could I hope you will pick up
>> https://issues.apache.org/jira/browse/IGNITE-8509?
>>
>> чт, 24 мая 2018 г. в 14:00, Maxim Muzafarov :
>>
>>> Hello,
>>>
>>> Just bump this topic up.
>>>
>>> 6/10 execution timeouts for the last 10 build in master!
>>>
>>> Will anyone help?
>>>
>>> [1]
>>>
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache6=1=buildTypeHistoryList_IgniteTests24Java8=%3Cdefault%3E
>>>
>>> пн, 21 мая 2018 г. в 12:58, Dmitry Pavlov :
>>>
>>> > Hi Maxim,
>>> >
>>> > I observe the same, Cache 6 critical recent fails: 18,0% [9 fails / 50
>>> > runs]
>>> >
>>> > I hope Aleksei Scherbakov can help here. Alexey, please step in.
>>> >
>>> > Sincerely,
>>> > Dmitriy Pavlov
>>> >
>>> > вс, 20 мая 2018 г. в 20:37, Maxim Muzafarov :
>>> >
>>> > > Hello Igniters,
>>> > >
>>> > > Have anyone noticed a lot of execution timeouts for Cache 6 Suite?
>>> > > Since recently it fails too much on TxRollbackOnTimeoutNearCacheTest
>>> with
>>> > > "Found long running transaction".
>>> > >
>>> > > Please refer to TC [1]. It has 4/10 execution timeouts for the last
>>> 10
>>> > > builds in master.
>>> > >
>>> > > I've created IGNITE-8509 [2]. Will someone have time to look at? Or
>>> I'll
>>> > > try when I'm get free.
>>> > >
>>> > > [1]
>>> > >
>>> > >
>>> >
>>> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Cache6_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv
>>> > > [2] https://issues.apache.org/jira/browse/IGNITE-8509
>>> > >
>>> >
>>>
>>
>
> --
>
> Best regards,
> Alexei Scherbakov
>

Re: RDD spark 2.10 version upgrade & TC suites

[Dmitry Pavlov]

I guess related topic is
http://apache-ignite-developers.2346864.n4.nabble.com/Review-request-for-IGNITE-8534-Upgrade-Ignite-Spark-Module-s-Spark-version-to-2-3-td30979.html
 Review request for IGNITE-8534 Upgrade Ignite Spark Module's Spark version
to 2.3.
and ticket https://issues.apache.org/jira/browse/IGNITE-8534


чт, 12 июл. 2018 г. в 19:35, Denis Magda :

> Nikolay,
>
> Please step in. I still see spark-2.10 module which means we fully support
> this version.
>
> --
> Denis
>
> On Thu, Jul 12, 2018 at 9:31 AM Dmitry Pavlov 
> wrote:
>
> > Hi Igniters,
> >
> > Do we need
> >
> >
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210=%3Cdefault%3E=buildTypeStatusDiv
> > suite is always fails with exit code 1 and I think I saw discussion about
> > version change.
> >
> > Could I remove this suite from RunAll?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
>

Re: Delete ticket - issues.apache.org

[Dmitry Pavlov]

Hi, I'm not sure it is possible to delete issue in Apache JIRA.

I can suggest to resolve it as Wont' fix.

Sincerely,
Dmitriy Pavlov

ср, 20 июн. 2018 г. в 11:15, Puviarasu S :

> Hi Team,
>
> I have created a ticket in https://issues.apache.org/jira. I am in a
> situation to delete the ticket such that it is not accessible over the
> Internet.
>
> Kindly requesting you to help me in deleting the ticket from Apache JIRA.
>
> Thanks in advance!!!
>
> Regards,
> Puviarasu
>

Re: Wiki edit permissions

[Denis Magda]

Hi,

You're in. Not you should be able to edit the page. Let me know if you
still have any issue.

--
Denis

On Thu, Jul 12, 2018 at 6:54 AM kondako...@mail.ru.INVALID
 wrote:

> Hi Igniters!
>
> I'm working on Ignite MVCC feature. Recently I've implemented a
> coordinator failover support (IGNITE-6754) and I would like to add a
> couple words in our wiki about how does it work. But unfortunately I am
> not allowed to edit this page:
>
> https://cwiki.apache.org/confluence/display/IGNITE/Distributed+MVCC+And+Transactional+SQL+Design
>
> Could you please grant me these permissions? My id is rkondakov.
>
> Thank you.
>
> --
> Kind regards,
> Roman Kondakov
>
>
>

[jira] [Created] (IGNITE-8994) Configuring dedicated volumes for WAL and data with Kuberenetes

[Denis Magda (JIRA)]

Denis Magda created IGNITE-8994:
---

 Summary: Configuring dedicated volumes for WAL and data with 
Kuberenetes
 Key: IGNITE-8994
 URL: https://issues.apache.org/jira/browse/IGNITE-8994
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
 Fix For: 2.7


The current StatefulSet documentation request only one persistent volume for 
both WAL and data/index files:
https://apacheignite.readme.io/docs/stateful-deployment#section-statefulset-deployment

However, according to Ignite performance guide the WAL has to be located on a 
dedicated volume:
https://apacheignite.readme.io/docs/durable-memory-tuning#section-separate-disk-device-for-wal

Provide StatefulSet configuration that shows how to request separate volumes 
for the WAL and data/index files. If needed, provide YAML configs for 
StorageClass and volume claims.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8993) Configuring sticky LoadBalancer for Ignite Service with Kubernetes

[Denis Magda (JIRA)]

Denis Magda created IGNITE-8993:
---

 Summary: Configuring sticky LoadBalancer for Ignite Service with 
Kubernetes
 Key: IGNITE-8993
 URL: https://issues.apache.org/jira/browse/IGNITE-8993
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
 Fix For: 2.7


Ignite service used for Ignite pods auto-discovery and access to the cluster 
from remote applications is deployed as LoadBalancer:
https://apacheignite.readme.io/docs/ignite-service

This might lead to problems when a stateful session is needed between an app 
and the cluster. For instance, Ignite JDBC driver preserves the state of an 
opened connection meaning that once LoadBalancer connects the driver to an 
Ignite pod, all the queries have to be redirected to that Ignite pod only 
(unless the pod is down).

We need to show how to configure a sticky LoadBalancer that will assign a 
client connection to a specific pod and won't change it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] ignite pull request #4353: Ignite-8685: backporting

[sk0x50]

GitHub user sk0x50 opened a pull request:

https://github.com/apache/ignite/pull/4353

Ignite-8685: backporting



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-8685-backport

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4353.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 #4353


commit 2f1ea2cdb76863008d4514f26845457bdeb7d6ed
Author: Andrey Novikov 
Date:   2018-01-19T04:35:30Z

IGNITE-6920 Minor fix.

(cherry picked from commit 9cc7cbf)

commit 62652f3fb1563ba149dcbccb80928d50b822ff36
Author: alexdel 
Date:   2018-01-25T08:49:28Z

IGNITE-7064 Web Console: Implemented basic E2E tests.

(cherry picked from commit ce96e4f)

commit 06e891f1161af598e0aa4665f7a6047637d1c476
Author: Dmitriy Shabalin 
Date:   2018-01-25T09:51:44Z

IGNITE-7522 Web Console: Fixed cluster selector state after cluster restart.

(cherry picked from commit ac3cfb8)

commit 291cb2c88118ccffebcf3383db629647faec1eee
Author: Dmitriy Shabalin 
Date:   2018-01-25T10:33:13Z

IGNITE-7529 Web Console: Refactor UIGrid column filters.

(cherry picked from commit 08658ea)

commit 443eafc718685e66c9a60058bd0ab56d88f9f0a6
Author: alexdel 
Date:   2018-01-25T14:38:36Z

IGNITE-7064 Web Console: Minor test fix.

(cherry picked from commit 4b6d9ad)

commit 6f1df5c40100363b5922734223a774ff1d6a008e
Author: Ilya Borisov 
Date:   2018-01-26T09:07:47Z

IGNITE-7031 Web Console: Refactored confirmation cancellation logic.

(cherry picked from commit 92ae3fe)

commit 16982825fb06ff2724ba4583781cc15443c4f46d
Author: Alexey Kuznetsov 
Date:   2018-02-02T10:07:57Z

IGNITE-7610 Web Console: Profile page refactored to component.

(cherry picked from commit 958975e)

commit 9c6a52250e058c4546aef0d0ecee977c07076a1a
Author: Alexey Kuznetsov 
Date:   2018-02-02T10:09:37Z

IGNITE-7612 Web Console: Refactored mongoose schemas to separate module.

(cherry picked from commit 71db707)

commit 89e15830dedcb46f24d9cc9b922ba3b013331a18
Author: Vasiliy Sisko 
Date:   2018-02-12T10:22:10Z

Web Agent: Fixed wrong config of IGNITE_ATOMIC_CACHE_DELETE_HISTORY_SIZE in 
demo startup.

(cherry picked from commit 1a6e544)

commit 18966673570425192e1b89fbb2c63d164b47eaca
Author: Vasiliy Sisko 
Date:   2018-02-12T13:24:30Z

IGNITE-7578 Actualized client connector configuration.

(cherry picked from commit 819d746)

commit 237063efa35c54bb9e9800ecf63ea223ec20a9ef
Author: alexdel 
Date:   2018-02-19T04:25:24Z

IGNITE-7650 Extracted signin/signup form to separate page, improved landing 
page.

(cherry picked from commit 1925674)

commit 679aeca7a3ff60a9dd478966d3949107d302d5db
Author: Andrey Novikov 
Date:   2018-02-19T07:56:07Z

IGNITE-7650 Fixed headers.

(cherry picked from commit 67922b3)

commit 5d5a6a05ec49f895e8a5edd505e496dcfe58a208
Author: Vasiliy Sisko 
Date:   2018-02-21T04:21:02Z

IGNITE-6094 Web Agent: Enabled persistent in demo mode.

(cherry picked from commit 3c35900)

commit e35d8cfb06f52765959fc2e1883bf70fe0259f45
Author: Alexander Kalinin 
Date:   2018-02-21T07:03:20Z

IGNITE-7320 Web Console - Fixed table headers for Safari.

(cherry picked from commit 04a025b)

commit 20cb1439f48b9a3c985f65784af36ef2c6f45e4f
Author: Andrey Novikov 
Date:   2018-02-22T02:54:05Z

IGNITE-7650 Fixed counties codes.

(cherry picked from commit fc40261)

commit 50d1389cd60e148005701e3450c8ae9998fd5fc9
Author: Alexey Kuznetsov 
Date:   2018-02-22T03:28:32Z

IGNITE-6287 Web Console: Fixed regression for EXPLAIN.

(cherry picked from commit 2bee8f8)

commit 330e502d5effea485254151ebf9b666e67d68475
Author: Alexander Kalinin 
Date:   2018-02-26T08:13:52Z

IGNITE-7729. Web Console. Added roles support in E2E tests.

(cherry picked from commit a83b264)

commit 3579db951abec81b7201ad91326ddc73ee828387
Author: Vasiliy Sisko 
Date:   2018-01-26T03:22:50Z

IGNITE-7392 Visor Cmd: Added missing word 'factory'.

(cherry picked from commit c0b14e5)

commit c125fa2068b62ab5286888ab2a16b5b034964dfd
Author: Vasiliy Sisko 
Date:   2018-02-12T03:13:06Z

IGNITE-2093 Visor CMD: Added support to scan near cache.

(cherry picked from commit a5a907b)

commit 2f074c05492439e1860a6920fff2861a071b58a8
Author: Alexey Kuznetsov 
Date:   2018-02-28T11:53:26Z

IGNITE-7578 Backport for ignite-2.4.3.

commit 8b1e77bac2d4fe125463f8978ca905d34a45b82f
Author: Alexey Kuznetsov 
Date:   2018-02-28T11:57:53Z

ignite-2.4.3 Fixed versions list.

commit bad7053586cccbbae4eb3d6dcba0d1ada5d2d2f2
Author: Alexey Kuznetsov 
Date:   2018-03-01T09:18:17Z

IGNITE-6920 Fixed missed require.

(cherry picked from commit fe89fc4)

Re: Quick questions on segments and page map buckets

[Dmitry Pavlov]

Hi, I've double checked code regarding question 1:

PageMemoryImpl#segments segments count (len) comes from sizes array len.
Sizes array come to page memory from
GridCacheDatabaseSharedManager.calculateFragmentSizes(). This method which
gets availableProcessors from runtime (CPU count). I didn't find any shift
to SEG_BITS.

It can be chaged by DataStorageConfiguration.setConcurrencyLevel() but by
default is the same with #CPU.

Which is why I mentioned segments count = CPU count by default in wiki.

Recenly some member of community proposed update to offical doc about
segments count. So now it states #segments=#CPU.

So I guess for 8 CPU we will have 8 segments.

Please correct me if I missing something.

Sincerely,
Dmitriy Pavlov

ср, 27 июн. 2018 г. в 15:30, Eduard Shangareev :

> Dmitry,
>
> I mean Chugunov, but I have questioned him. His answer was the A. Goncharuk
> should now the answer.
>
> On Wed, Jun 27, 2018 at 2:58 PM, Dmitry Pavlov 
> wrote:
>
> > John, is this question still actual?
> >
> > пт, 22 июн. 2018 г. в 15:18, Dmitry Pavlov :
> >
> > > Hi Ed,
> > >
> > > Which Sergey do you mean? I know a number of contributors.
> > >
> > > Sincerely,
> > >
> > >
> > > вт, 19 июн. 2018 г. в 22:15, Eduard Shangareev <
> > > eduard.shangar...@gmail.com>:
> > >
> > >> Hi,
> > >>
> > >> 1. It looks weird, yeah. Need to ask Sergey, who has changed it last
> > time.
> > >>
> > >> 2. Because we could reuse memory. For example, after cache destroy or
> > >> something like that.
> > >>
> > >> On Tue, Jun 19, 2018 at 9:58 PM, John Wilson  >
> > >> wrote:
> > >>
> > >> > Hi,
> > >> >
> > >> > Two quick questions:
> > >> >
> > >> >
> > >> >1. The design documentation here,
> > >> >https://cwiki.apache.org/confluence/display/IGNITE/
> > >> > Ignite+Durable+Memory+-+under+the+hood,
> > >> >states that the default segment count is equal to the number of
> > >> logical
> > >> >cores available in the underlying machine. However, the segments
> > >> array
> > >> > in
> > >> >PageMemory indicates that the maximum number of segments is: 1 <<
> > >> > SEG_BITS.
> > >> >Since SEG_BITS = 4, the max # segments is 16. Did I miss
> something
> > >> here?
> > >> >2. Reading the code in PageMemoryNoStoreImp, it looks like pages
> > are
> > >> >allocated segment sequentially in a bump-the-pointer strategy
> where
> > >> the
> > >> >first 8 bytes of a segment hold a pointer to the index of the
> last
> > >> >allocated page. If this is true, then I don't understand the
> point
> > of
> > >> >having a page map buckets. Why not use a simple arithmetic index
> *
> > >> > pageSize
> > >> >to get the offset of a page?
> > >> >
> > >> > Thanks.
> > >> > John
> > >> >
> > >>
> > >
> >
>

Re: Async cache groups rebalance not started with rebalanceOrder ZERO

[Dmitry Pavlov]

Hi Ilya,

Do you know, what is correct: behaviour or javadoc?

Sincerely,
Dmitriy Pavlov

пн, 9 июл. 2018 г. в 16:43, Maxim Muzafarov :

> Hello Igniters,
>
> Each cache group has “rebalance order” property. As javadoc for
> getRebalanceOrder() says: “Note that cache with order {@code 0} does not
> participate in ordering. This means that cache with rebalance order {@code
> 0} will never wait for any other caches. All caches with order {@code 0}
> will be rebalanced right away concurrently with each other and ordered
> rebalance processes. If not set, cache order is 0, i.e. rebalancing is not
> ordered.”
>
> In fact GridCachePartitionExchangeManager always build the chain of
> rebalancing cache groups to start (even for cache order ZERO):
>
> ignite-sys-cache -> cacheR -> cacheR3 -> cacheR2 -> cacheR5 -> cacheR1.
>
> If one of these groups will fail to start further groups will never be run.
>
> * Question 1*: Should we fix javadoc description or create a bug for fixing
> such rebalance behavior?
>
> [1]
>
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/processors/cache/GridCachePartitionExchangeManager.java#L2630
>

Re: RDD spark 2.10 version upgrade & TC suites

[Denis Magda]

Nikolay,

Please step in. I still see spark-2.10 module which means we fully support
this version.

--
Denis

On Thu, Jul 12, 2018 at 9:31 AM Dmitry Pavlov  wrote:

> Hi Igniters,
>
> Do we need
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210=%3Cdefault%3E=buildTypeStatusDiv
> suite is always fails with exit code 1 and I think I saw discussion about
> version change.
>
> Could I remove this suite from RunAll?
>
> Sincerely,
> Dmitriy Pavlov
>

RDD spark 2.10 version upgrade & TC suites

[Dmitry Pavlov]

Hi Igniters,

Do we need
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_RddSpark210=%3Cdefault%3E=buildTypeStatusDiv
suite is always fails with exit code 1 and I think I saw discussion about
version change.

Could I remove this suite from RunAll?

Sincerely,
Dmitriy Pavlov

Re: MTCGA: new failures in builds [1479951] needs to be handled

[Dmitry Pavlov]

I've pushed fix of failure to master.

чт, 12 июл. 2018 г. в 16:25, Dmitry Pavlov :

> Hi Igniters,
>
> this notification was generated because this test was stable passing (at
> least 5 ok) in master and became stable failed (at least 3 failures).
>
> Such notifications would not be generated for each case of flaky failures,
> so I hope this feature will help us to identify and fix new failures.
>
> I'll fix message format to be more readable soon.
>
> It would be pleasure to me to run short talk (webinar) about tests, MTCGA,
> and MTCGA.Bot (Ignite TC helper). Please reply if you are interested.
>
> I would also highly appreciate any kind of feedback.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 12 июл. 2018 г. в 16:14, :
>
>> Hi Ignite Developer,
>>
>> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
>> I hope you can help.
>>
>>  *New test failure in master
>> IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
>>
>> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1615751728537497724=%3Cdefault%3E=testDetails
>>  Changes may led to failure were done by alexey.goncharuk
>> http://ci.ignite.apache.org/viewModification.html?modId=825445=false,
>> eshangareev
>> http://ci.ignite.apache.org/viewModification.html?modId=825442=false,
>> sergey.chugunov
>> http://ci.ignite.apache.org/viewModification.html?modId=825439=false,
>> irakov
>> http://ci.ignite.apache.org/viewModification.html?modId=825436=false,
>> irakov
>> http://ci.ignite.apache.org/viewModification.html?modId=825428=false,
>> ivandasch
>> http://ci.ignite.apache.org/viewModification.html?modId=825411=false,
>> sbt-pereslegin-pa1
>> http://ci.ignite.apache.org/viewModification.html?modId=825407=false,
>> alexey.scherbakoff
>> http://ci.ignite.apache.org/viewModification.html?modId=825404=false,
>> akuznetsov
>> http://ci.ignite.apache.org/viewModification.html?modId=825396=false,
>> vsisko
>> http://ci.ignite.apache.org/viewModification.html?modId=825371=false,
>> pivanov
>> http://ci.ignite.apache.org/viewModification.html?modId=825366=false,
>> dmitriyff
>> http://ci.ignite.apache.org/viewModification.html?modId=825351=false,
>> dmitriyff
>> http://ci.ignite.apache.org/viewModification.html?modId=825348=falseIf
>> your changes can led to this failure(s), please create issue with label
>> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
>> set ticket to PA state and write to dev list fix is readyFor case
>> fix will require some time please mute test and set label Muted_Test to
>> issueIf you know which change caused failure please
>> contact change author directlyIf you don't know which change
>> caused failure please send message to dev list to find
>> outShould you have any questions please contact
>> dpav...@apache.org or write to dev.listBest
>> Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23 MSK
>> 2018
>
>

Re: PR Reivew https://github.com/apache/ignite/pull/4300

[Dmitry Pavlov]

Hi,

Yes, correct. In the same time I've checked branch state with custom tool,
so we can be pretty sure change does not introduce new failures.

I merged your changes, in the same time I needed to do several updates in
code (see details in ticket comments).

Looking forward to your contributions!

Sincerely,
Dmitriy Pavlov

P.S. Additional references for you that should boost your onboarding.

https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines

https://cwiki.apache.org/confluence/display/IGNITE/Abbreviation+Rules

https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute


чт, 12 июл. 2018 г. в 13:32, Ken Cheng :

> Thank you very much!
>
> If it's the case of what you said, a merge from latest main to this branch
> will fix this issue?
>
> Thanks,
> Ken Cheng
>
>
> On Thu, Jul 12, 2018 at 6:16 PM Dmitry Pavlov 
> wrote:
>
> > Hi,
> >
> > I've checked this results and I guess branch was created at some unlucky
> > moment, and currently most of timeouts were fixed in master.
> >
> > "No changes" mean Teamcity does not detected changes between runs.
> Probably
> > I've scheduled re-run for some particular suites more than one time.
> >
> > I'll take a look to PR itself.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 12 июл. 2018 г. в 11:39, kcheng.mvp :
> >
> > > Here is the latest TC result
> > >
> > >
> > > The high-lighted part shows as  "no changes", which mean my changes
> would
> > > not cause the failure, right?
> > >
> > >
> > >
> > >
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1480732=buildResultsDiv=IgniteTests24Java8_RunAll
> > >  >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> > >
> >
>

[GitHub] ignite pull request #4300: Ignite 8776:Eviction policy MBeans are never regi...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4300


---

Re: Ignite guide for community developes

[vgrigorev]

Hi colleges!

I would like move topic to suitable place.

Please only clarify how to do it:
In a page about creating IEP 
link

   
There are no appropriate information.

If you can do it please do.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Start contributing to Apache Ignite

[Dmitry Pavlov]

Hi Igniters,

bumping up. Issue is still in PA.

Ed has looked to patch and add some changes. Who could pick up this review?

Sincerely,
Dmitriy Pavlov

вт, 12 сент. 2017 г. в 11:43, Mikhail Lipkovich :

> Thanks a lot Denis!
>
> Will try to do something useful
>
> Mikhail
>
> 2017-09-12 3:41 GMT+03:00 Denis Magda :
>
> > Mikhail, welcome!
> >
> > Granted you required permissions! Look forward to your contributions!
> >
> > —
> > Denis
> >
> > > On Sep 11, 2017, at 4:33 AM, Mikhail Lipkovich <
> > lipkovich.mikh...@gmail.com> wrote:
> > >
> > > Hello,
> > >
> > > I would like to start contributing to Ignite.
> > > This issue seems suitable for me
> > > https://issues.apache.org/jira/browse/IGNITE-6284
> > >
> > > Can I get permissions to assign issues to myself?
> > >
> > > My username at issues.apache.org is mlipkovich
> > > Full name is Mikhail Lipkovich
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Mikhail
> >
> >
>

Re: Ignite guide for community developes

[Dmitry Pavlov]

Hi Igniters,

I totally agree with Yakov and vgrigorev.

Could you share wiki ID so you can contribute these proposals at least as
Ignite Enhancement Proposal (IEP)?

You can share your apache wiki ID to add contibutor permission, so you will
be able to create wiki page.

Would you like to contribute some from proposed topics as wiki pages or
separate guide?

Sincerely,
Dmitriy Pavlov

чт, 12 июл. 2018 г. в 15:13, Yakov Zhdanov :

> Hi!
>
> Can you please move you proposal to Apache Ignite Wiki as new IEP? So that
> community can discuss and comment? Eventually we will end up with a plan on
> creating the guide. What do you think?
>
> --Yakov
>
> 2018-07-12 12:24 GMT+03:00 vgrigorev :
>
> > Very many developers have desire to participate in Ignite development but
> > tries of this is typically not successful due to big barrier to begin
> > develop to such a complex project.During Moscow Ignite Meetup #3  we were
> > discussed with GridGain presenters that for attracting community to
> > development process  creating a good guide can be crucial and I want to
> > propose create such a guide.For the proposal to be more concrete and
> > substantial I write document with my vision of basic organization,
> problem
> > aspects that stops developers, sample of such documentation from really
> > successful community.File is attached.Please consider and discuss
> > Proposal_for_Ignite_development_guide.docx
> >  > com/file/t544/Proposal_for_Ignite_development_guide.docx>
> > this proposal.
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

Wiki edit permissions

[kondako...@mail.ru.INVALID]

Hi Igniters!

I'm working on Ignite MVCC feature. Recently I've implemented a 
coordinator failover support (IGNITE-6754) and I would like to add a 
couple words in our wiki about how does it work. But unfortunately I am 
not allowed to edit this page: 
https://cwiki.apache.org/confluence/display/IGNITE/Distributed+MVCC+And+Transactional+SQL+Design


Could you please grant me these permissions? My id is rkondakov.

Thank you.

--
Kind regards,
Roman Kondakov

Re: MTCGA: new failures in builds [1479951] needs to be handled

[Dmitry Pavlov]

Hi Igniters,

this notification was generated because this test was stable passing (at
least 5 ok) in master and became stable failed (at least 3 failures).

Such notifications would not be generated for each case of flaky failures,
so I hope this feature will help us to identify and fix new failures.

I'll fix message format to be more readable soon.

It would be pleasure to me to run short talk (webinar) about tests, MTCGA,
and MTCGA.Bot (Ignite TC helper). Please reply if you are interested.

I would also highly appreciate any kind of feedback.

Sincerely,
Dmitriy Pavlov

чт, 12 июл. 2018 г. в 16:14, :

> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
>  *New test failure in master
> IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
>
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1615751728537497724=%3Cdefault%3E=testDetails
>  Changes may led to failure were done by alexey.goncharuk
> http://ci.ignite.apache.org/viewModification.html?modId=825445=false,
> eshangareev
> http://ci.ignite.apache.org/viewModification.html?modId=825442=false,
> sergey.chugunov
> http://ci.ignite.apache.org/viewModification.html?modId=825439=false,
> irakov
> http://ci.ignite.apache.org/viewModification.html?modId=825436=false,
> irakov
> http://ci.ignite.apache.org/viewModification.html?modId=825428=false,
> ivandasch
> http://ci.ignite.apache.org/viewModification.html?modId=825411=false,
> sbt-pereslegin-pa1
> http://ci.ignite.apache.org/viewModification.html?modId=825407=false,
> alexey.scherbakoff
> http://ci.ignite.apache.org/viewModification.html?modId=825404=false,
> akuznetsov
> http://ci.ignite.apache.org/viewModification.html?modId=825396=false,
> vsisko
> http://ci.ignite.apache.org/viewModification.html?modId=825371=false,
> pivanov
> http://ci.ignite.apache.org/viewModification.html?modId=825366=false,
> dmitriyff
> http://ci.ignite.apache.org/viewModification.html?modId=825351=false,
> dmitriyff
> http://ci.ignite.apache.org/viewModification.html?modId=825348=falseIf
> your changes can led to this failure(s), please create issue with label
> MakeTeamCityGreenAgain and assign it to you.If you have fix, please
> set ticket to PA state and write to dev list fix is readyFor case
> fix will require some time please mute test and set label Muted_Test to
> issueIf you know which change caused failure please
> contact change author directlyIf you don't know which change
> caused failure please send message to dev list to find
> outShould you have any questions please contact
> dpav...@apache.org or write to dev.listBest
> Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23 MSK
> 2018

Re: Contribution

[Павлухин Иван]

Hi Dmitriy,

Thanks a lot!

2018-07-12 16:20 GMT+03:00 Dmitry Pavlov :

> Hi Ivan,
>
> Welcome to the Ignite Community.
>
> I've added you to contributors list, so you can now assign issue to
> yourself.
>
> Looking forward to your contributions!
>
> Sincerely,
> Dmitriy Pavlov
>
> P.S. Additional references for you that should boost your onboarding.
>
> Please subscribe to both dev and user lists:
> https://ignite.apache.org/community/resources.html#mail-lists
>
> Get familiar with Ignite development process described here:
> https://cwiki.apache.org/confluence/display/IGNITE/Development+Process
>
> Instructions on how to contribute can be found here:
> https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute
>
> Project setup in Intellij IDEA:
> https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup
>
>
> чт, 12 июл. 2018 г. в 16:08, Павлухин Иван :
>
> > Hi Igniters,
> >
> > I would like to start working on
> > https://issues.apache.org/jira/browse/IGNITE-8581
> > My name in Jira is Pavlukhin
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>



-- 
Best regards,
Ivan Pavlukhin

Re: Contribution

[Dmitry Pavlov]

Hi Ivan,

Welcome to the Ignite Community.

I've added you to contributors list, so you can now assign issue to
yourself.

Looking forward to your contributions!

Sincerely,
Dmitriy Pavlov

P.S. Additional references for you that should boost your onboarding.

Please subscribe to both dev and user lists:
https://ignite.apache.org/community/resources.html#mail-lists

Get familiar with Ignite development process described here:
https://cwiki.apache.org/confluence/display/IGNITE/Development+Process

Instructions on how to contribute can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute

Project setup in Intellij IDEA:
https://cwiki.apache.org/confluence/display/IGNITE/Project+Setup


чт, 12 июл. 2018 г. в 16:08, Павлухин Иван :

> Hi Igniters,
>
> I would like to start working on
> https://issues.apache.org/jira/browse/IGNITE-8581
> My name in Jira is Pavlukhin
>
> --
> Best regards,
> Ivan Pavlukhin
>

MTCGA: new failures in builds [1479951] needs to be handled

[dpavlov . tasks]

Hi Ignite Developer,

I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I 
hope you can help.

 *New test failure in master 
IgnitePdsCheckpointSimulationWithRealCpDisabledTest.testCheckpointSimulationMultiThreaded
 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1615751728537497724=%3Cdefault%3E=testDetails
 Changes may led to failure were done by alexey.goncharuk 
http://ci.ignite.apache.org/viewModification.html?modId=825445=false, 
eshangareev 
http://ci.ignite.apache.org/viewModification.html?modId=825442=false, 
sergey.chugunov 
http://ci.ignite.apache.org/viewModification.html?modId=825439=false, 
irakov 
http://ci.ignite.apache.org/viewModification.html?modId=825436=false, 
irakov 
http://ci.ignite.apache.org/viewModification.html?modId=825428=false, 
ivandasch 
http://ci.ignite.apache.org/viewModification.html?modId=825411=false, 
sbt-pereslegin-pa1 
http://ci.ignite.apache.org/viewModification.html?modId=825407=false, 
alexey.scherbakoff 
http://ci.ignite.apache.org/viewModification.html?modId=825404=false, 
akuznetsov 
http://ci.ignite.apache.org/viewModification.html?modId=825396=false, 
vsisko 
http://ci.ignite.apache.org/viewModification.html?modId=825371=false, 
pivanov 
http://ci.ignite.apache.org/viewModification.html?modId=825366=false, 
dmitriyff 
http://ci.ignite.apache.org/viewModification.html?modId=825351=false, 
dmitriyff 
http://ci.ignite.apache.org/viewModification.html?modId=825348=falseIf
 your changes can led to this failure(s), please create issue with label 
MakeTeamCityGreenAgain and assign it to you.If you have fix, please set 
ticket to PA state and write to dev list fix is readyFor case fix will 
require some time please mute test and set label Muted_Test to 
issueIf you know which change caused failure please contact 
change author directlyIf you don't know which change caused failure 
please send message to dev list to find outShould you have any 
questions please contact dpav...@apache.org or write to dev.listBest 
Regards,MTCGA.BotNotification generated at Thu Jul 12 16:14:23 MSK 
2018

Contribution

[Павлухин Иван]

Hi Igniters,

I would like to start working on
https://issues.apache.org/jira/browse/IGNITE-8581
My name in Jira is Pavlukhin

-- 
Best regards,
Ivan Pavlukhin

Re: Add cluster (de)activation events IGNITE-8376

[Dmitriy Setrakyan]

On Thu, Jul 12, 2018 at 3:22 PM, Yakov Zhdanov  wrote:

> If events are working when grid is not active and adding/removing listeners
> is also possible then I agree/
>

The events should be working. The cluster is not active, but the node is
started and should be able to fire events.

AG, can you comment?

Re: Add cluster (de)activation events IGNITE-8376

[Yakov Zhdanov]

If events are working when grid is not active and adding/removing listeners
is also possible then I agree/

--Yakov

Re: Add cluster (de)activation events IGNITE-8376

[Dmitriy Setrakyan]

On Thu, Jul 12, 2018 at 3:08 PM, Yakov Zhdanov  wrote:

> Its counter event on_after_deactivated cannot be fired through event
> notification support. Therefore, it is better to gather such events in
> LifeCycleEventType.
>

Why not? After deactivation the node should still be usable and should be
able to fire events. Can you explain?

Re: Ignite guide for community developes

[Yakov Zhdanov]

Hi!

Can you please move you proposal to Apache Ignite Wiki as new IEP? So that
community can discuss and comment? Eventually we will end up with a plan on
creating the guide. What do you think?

--Yakov

2018-07-12 12:24 GMT+03:00 vgrigorev :

> Very many developers have desire to participate in Ignite development but
> tries of this is typically not successful due to big barrier to begin
> develop to such a complex project.During Moscow Ignite Meetup #3  we were
> discussed with GridGain presenters that for attracting community to
> development process  creating a good guide can be crucial and I want to
> propose create such a guide.For the proposal to be more concrete and
> substantial I write document with my vision of basic organization, problem
> aspects that stops developers, sample of such documentation from really
> successful community.File is attached.Please consider and discuss
> Proposal_for_Ignite_development_guide.docx
>  com/file/t544/Proposal_for_Ignite_development_guide.docx>
> this proposal.
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: Add cluster (de)activation events IGNITE-8376

[Yakov Zhdanov]

Its counter event on_after_deactivated cannot be fired through event
notification support. Therefore, it is better to gather such events in
LifeCycleEventType.

--Yakov

Re: Cases of using AffinityAssignment.clientEventChange method

[Dmitry Pavlov]

Sute. I like this idea, let's wait.

чт, 12 июл. 2018 г. в 14:48, Maxim Muzafarov :

> Dmity,
>
> Thank you for reply. I've maked this ticket with "newbie" tag.
>
> I would like to keep this ticket for our new community members. Change is
> really simple, so we can easily guide new mebers the development processes
> adopted by our community.
>
> Hope this issue will find its author.
> If not I'll do it by myself.
>
>
> пт, 6 июл. 2018 г. в 16:09, Dmitry Pavlov :
>
> > Hi Maxim,
> >
> > Thank you for your efforts to finding this out. I also didn't find any
> > usages, so I agree here.
> >
> > I'm going to commit this by lazy consensus if no-one objects within the
> > next three days.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 5 июл. 2018 г. в 12:56, Maxim Muzafarov :
> >
> > > Hello everyone,
> > >
> > > Suppose clientEventChange method is useless and have confusing name.
> > >
> > > I'm suggesting to remove it as not used. I've filed issue for it:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-8936
> > >
> > >
> > > чт, 28 июн. 2018 г. в 16:53, Maxim Muzafarov :
> > >
> > > > Hi Igniters,
> > > >
> > > > Recently I've faced with AffinityAssignment.clientEventChange()
> method
> > > and
> > > > not completly sure about the range of its applicability. The javadoc
> > says
> > > > "return {@code True} if related discovery event did not cause
> affinity
> > > > assignment change and this assignment is just reference to the
> previous
> > > > one."
> > > >
> > > > Three facts about it:
> > > > 1) Method is the part of internal Ignite API
> > > > 2) It​ is​ not used anywhere in Ignite project code
> > > > 3) "clientEventChage" confusing name for this method. "true" value
> can
> > be
> > > > set not only by client-related events (e.g. cacheChangeRequest,
> > > > affinityChangeRequest etc.).
> > > >
> > > > I've prepared diagram when it has "TRUE" value [1].
> > > >
> > > > * Question #1 * When and for what cases we can use returned value of
> > this
> > > > method?
> > > > * Question #2 * Can it be removed? My suggestion is to keep internal
> > API
> > > > as simple as possible.
> > > >
> > > >
> > > > [1] https://image.ibb.co/cW6Mx8/Client_Event_Change_1.png
> > > >
> > >
> >
>

Re: Cases of using AffinityAssignment.clientEventChange method

[Maxim Muzafarov]

Dmity,

Thank you for reply. I've maked this ticket with "newbie" tag.

I would like to keep this ticket for our new community members. Change is
really simple, so we can easily guide new mebers the development processes
adopted by our community.

Hope this issue will find its author.
If not I'll do it by myself.


пт, 6 июл. 2018 г. в 16:09, Dmitry Pavlov :

> Hi Maxim,
>
> Thank you for your efforts to finding this out. I also didn't find any
> usages, so I agree here.
>
> I'm going to commit this by lazy consensus if no-one objects within the
> next three days.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 5 июл. 2018 г. в 12:56, Maxim Muzafarov :
>
> > Hello everyone,
> >
> > Suppose clientEventChange method is useless and have confusing name.
> >
> > I'm suggesting to remove it as not used. I've filed issue for it:
> >
> > https://issues.apache.org/jira/browse/IGNITE-8936
> >
> >
> > чт, 28 июн. 2018 г. в 16:53, Maxim Muzafarov :
> >
> > > Hi Igniters,
> > >
> > > Recently I've faced with AffinityAssignment.clientEventChange() method
> > and
> > > not completly sure about the range of its applicability. The javadoc
> says
> > > "return {@code True} if related discovery event did not cause affinity
> > > assignment change and this assignment is just reference to the previous
> > > one."
> > >
> > > Three facts about it:
> > > 1) Method is the part of internal Ignite API
> > > 2) It​ is​ not used anywhere in Ignite project code
> > > 3) "clientEventChage" confusing name for this method. "true" value can
> be
> > > set not only by client-related events (e.g. cacheChangeRequest,
> > > affinityChangeRequest etc.).
> > >
> > > I've prepared diagram when it has "TRUE" value [1].
> > >
> > > * Question #1 * When and for what cases we can use returned value of
> this
> > > method?
> > > * Question #2 * Can it be removed? My suggestion is to keep internal
> API
> > > as simple as possible.
> > >
> > >
> > > [1] https://image.ibb.co/cW6Mx8/Client_Event_Change_1.png
> > >
> >
>

[GitHub] ignite pull request #4352: IGNITE-8992. Wrong log when LongJVMPauseDetector ...

[dgarus]

GitHub user dgarus opened a pull request:

https://github.com/apache/ignite/pull/4352

IGNITE-8992. Wrong log when LongJVMPauseDetector stops the worker thread



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/dgarus/ignite ignite-8992

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4352.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 #4352


commit 8f319f50c1e775e8bcbdc9371643312031129f02
Author: Garus Denis 
Date:   2018-07-12T11:34:47Z

IGNITE-8992. Wrong log when LongJVMPauseDetector stops the worker thread




---

Re: Add cluster (de)activation events IGNITE-8376

[Dmitriy Setrakyan]

On Mon, Jul 9, 2018 at 1:32 PM, Yakov Zhdanov  wrote:

> > What is the difference between a lifecycle even and regular events?
>
> Lifecycle events should be used when there is no opportunity for Ignite to
> fire regular event, e.g. node stops or is not started yet. Please see
> https://ignite.apache.org/releases/latest/javadoc/org/
> apache/ignite/lifecycle/LifecycleEventType.html


In this case I do not understand why activation should be a lifecycle
event. During activation Ignite has already started and events can be
reported using normal event notification support in Ignite, no?

D.

[GitHub] ignite pull request #4351: IGNITE-584 Correct results returned, while changi...

[zstan]

GitHub user zstan opened a pull request:

https://github.com/apache/ignite/pull/4351

IGNITE-584 Correct results returned, while changing topology



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-584

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4351.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 #4351


commit 1d71bc5966c335547f48292a12c7f2a5f5781130
Author: Evgeny Stanilovskiy 
Date:   2018-07-12T10:42:27Z

IGNITE-584 Correct results returned, while changing topology




---

[jira] [Created] (IGNITE-8992) Wrong log when LongJVMPauseDetector stops the worker thread

[Denis Garus (JIRA)]

Denis Garus created IGNITE-8992:
---

 Summary: Wrong log when LongJVMPauseDetector stops the worker 
thread
 Key: IGNITE-8992
 URL: https://issues.apache.org/jira/browse/IGNITE-8992
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Garus


When LongJVMPauseDetector stops the worker thread, a log will contain follow 
error:

[2018-07-12 
12:57:28,332][ERROR][jvm-pause-detector-worker][CacheMetricsEnableRuntimeTest1] 
jvm-pause-detector-worker has been interrupted
java.lang.InterruptedException: sleep interrupted
at java.lang.Thread.sleep(Native Method)
at 
org.apache.ignite.internal.LongJVMPauseDetector$1.run(LongJVMPauseDetector.java:97)

The error must be only if worker thread stopped unintentionally.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: PR Reivew https://github.com/apache/ignite/pull/4300

[Ken Cheng]

Thank you very much!

If it's the case of what you said, a merge from latest main to this branch
will fix this issue?

Thanks,
Ken Cheng


On Thu, Jul 12, 2018 at 6:16 PM Dmitry Pavlov  wrote:

> Hi,
>
> I've checked this results and I guess branch was created at some unlucky
> moment, and currently most of timeouts were fixed in master.
>
> "No changes" mean Teamcity does not detected changes between runs. Probably
> I've scheduled re-run for some particular suites more than one time.
>
> I'll take a look to PR itself.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 12 июл. 2018 г. в 11:39, kcheng.mvp :
>
> > Here is the latest TC result
> >
> >
> > The high-lighted part shows as  "no changes", which mean my changes would
> > not cause the failure, right?
> >
> >
> >
> >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1480732=buildResultsDiv=IgniteTests24Java8_RunAll
> > 
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>

Re: PR Reivew https://github.com/apache/ignite/pull/4300

[Dmitry Pavlov]

Hi,

I've checked this results and I guess branch was created at some unlucky
moment, and currently most of timeouts were fixed in master.

"No changes" mean Teamcity does not detected changes between runs. Probably
I've scheduled re-run for some particular suites more than one time.

I'll take a look to PR itself.

Sincerely,
Dmitriy Pavlov

чт, 12 июл. 2018 г. в 11:39, kcheng.mvp :

> Here is the latest TC result
>
>
> The high-lighted part shows as  "no changes", which mean my changes would
> not cause the failure, right?
>
>
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1480732=buildResultsDiv=IgniteTests24Java8_RunAll
> 
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[GitHub] ignite pull request #4262: IGNITE-8863 Tx rollback can cause remote tx hang.

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/ignite/pull/4262


---

Ignite guide for community developes

[vgrigorev]

Very many developers have desire to participate in Ignite development but
tries of this is typically not successful due to big barrier to begin
develop to such a complex project.During Moscow Ignite Meetup #3  we were
discussed with GridGain presenters that for attracting community to
development process  creating a good guide can be crucial and I want to
propose create such a guide.For the proposal to be more concrete and
substantial I write document with my vision of basic organization, problem
aspects that stops developers, sample of such documentation from really
successful community.File is attached.Please consider and discuss 
Proposal_for_Ignite_development_guide.docx

 
this proposal.



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: PR Reivew https://github.com/apache/ignite/pull/4300

[kcheng.mvp]

Here is the latest TC result


The high-lighted part shows as  "no changes", which mean my changes would
not cause the failure, right?



https://ci.ignite.apache.org/viewLog.html?buildId=1480732=buildResultsDiv=IgniteTests24Java8_RunAll
 



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-8991) Failed server node if predicate in scan query throw AssertionError

[Alexand Polyakov (JIRA)]

Alexand Polyakov created IGNITE-8991:


 Summary: Failed server node if predicate in scan query throw 
AssertionError
 Key: IGNITE-8991
 URL: https://issues.apache.org/jira/browse/IGNITE-8991
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.5
Reporter: Alexand Polyakov






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)