[jira] [Updated] (IGNITE-1776) [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes

2017-07-27 Thread Alexey Dmitriev (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Dmitriev updated IGNITE-1776:

Priority: Major  (was: Critical)

> [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails 
> sometimes
> ---
>
> Key: IGNITE-1776
> URL: https://issues.apache.org/jira/browse/IGNITE-1776
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.2
>
>
> TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails on TC 
> sometimes.
> Looks like a test bug, need just increase awaitTime(). I see Node FAILED 
> message exactly after 10 seconds. But it's strange that it's require too long 
> time. May be something wrong on agent.
> Logs:
> {noformat}
> junit.framework.AssertionFailedError: Latch count: 1
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.await(TcpClientDiscoverySpiSelfTest.java:2030)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer(TcpClientDiscoverySpiSelfTest.java:811)
> --- Stdout: ---
> [03:18:46,228][INFO ][main][root] >>> Starting test: 
> testClientNodeFailOneServer <<<
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] 
> >>>__    
> >>>   /  _/ ___/ |/ /  _/_  __/ __/  
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/   
> >>> 
> >>> ver. 1.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2015 Copyright(C) Apache Software Foundation
> >>> 
> >>> Ignite documentation: http://ignite.apache.org
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Config URL: n/a
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Daemon mode: off
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS: Mac OS X 10.7.5 
> x86_64
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS user: teamcity
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Language runtime: 
> Java Platform API Specification ver. 1.7
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM information: 
> Java(TM) SE Runtime Environment 1.7.0_67-b01 Oracle Corporation Java 
> HotSpot(TM) 64-Bit Server VM 24.65-b04
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM total memory: 
> 2.7GB
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Remote Management 
> [restart: off, REST: off, JMX (remote: off)]
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] 
> IGNITE_HOME=/Users/teamcity/buildAgent/work/871ff4a46e450b13
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM arguments: 
> [-DJAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home, 
> -DMCAST_GRP=229.116.1.2, -Dagent.home.dir=/Users/teamcity/buildAgent, 
> -Dagent.name=ip_192.168.1.116, -Dagent.ownPort=9090, 
> -Dagent.work.dir=/Users/teamcity/buildAgent/work, -Dbuild.number=3345, 
> -Dbuild.vcs.number=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb, 
> -Dbuild.vcs.number.1=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb, 
> -Dbuild.vcs.number.ApacheIgniteMirrorOnGitHub=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
>  
> -Dclassworlds.conf=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.m2.conf, 
> -Dcom.jetbrains.maven.watcher.report.file=/Users/teamcity/buildAgent/temp/buildTmp/maven-build-info.xml,
>  -Djava.io.tmpdir=/Users/teamcity/buildAgent/temp/buildTmp, 
> -Dmaven.home=/Users/teamcity/buildAgent/tools/maven3, 
> -Dmaven.repo.local=/Users/teamcity/.m2/repository, 
> -Dteamcity.agent.cpuBenchmark=605, 
> -Dteamcity.agent.dotnet.agent_url=http://localhost:9090/RPC2, 
> -Dteamcity.agent.dotnet.build_id=555612, 
> -Dteamcity.auth.password=j1gKlVPBOa3H6Wnrjp3Q3sK7ZqR4biuf, 
> -Dteamcity.auth.userId=TeamCityBuildId=555612, 
> -Dteamcity.build.changedFiles.file=/Users/teamcity/buildAgent/temp/buildTmp/changedFiles5940678572218707636.txt,
>  
> -Dteamcity.build.checkoutDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13,
>  -Dteamcity.build.id=555612, 
> -Dteamcity.build.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.build3844607694634646095.properties,
>  -Dteamcity.build.tempDir=/Users/teamcity/buildAgent/temp/buildTmp, 
> -Dteamcity.build.workingDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13, 
> -Dteamcity.buildConfName=Ignite SPI, -Dteamcity.buildType.id=Ignite_Spi, 
> -Dteamcity.configuration.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.config8915518964213838573.properties,
>  -Dteamcity.idea.home=/Users/teamcity/buildAgent/plugins/idea, 
>

[jira] [Updated] (IGNITE-537) Continuous processor should support p2p deployment on discovery data exchange

2017-07-26 Thread Alexey Dmitriev (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Dmitriev updated IGNITE-537:
---
Priority: Major  (was: Critical)

> Continuous processor should support p2p deployment on discovery data exchange
> -
>
> Key: IGNITE-537
> URL: https://issues.apache.org/jira/browse/IGNITE-537
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-4927) Write behind - need new mode without skipping values history

2017-04-06 Thread Alexey Dmitriev (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Dmitriev reassigned IGNITE-4927:
---

Assignee: Alexey Dmitriev

> Write behind - need new mode without skipping values history
> 
>
> Key: IGNITE-4927
> URL: https://issues.apache.org/jira/browse/IGNITE-4927
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Alexey Dmitriev
>
> Currently write behind store is backed by a map, therefore when several 
> updates come to the same key its values' change history is lost.
> We need to introduce optional mode and back write behind with a queue and 
> pass each  to database.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)