[jira] [Updated] (IGNITE-8533) Timeout collision in Client Nodes test suite
[ https://issues.apache.org/jira/browse/IGNITE-8533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Medvedev updated IGNITE-8533: Labels: MakeTeamcityGreenAgain (was: ) > Timeout collision in Client Nodes test suite > > > Key: IGNITE-8533 > URL: https://issues.apache.org/jira/browse/IGNITE-8533 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Medvedev >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.6 > > > IGNITE-8085 increased NODE_START_CHECK_LIMIT so "remote" node log is parsed > for longer (set now to 25 * 2000ms) > https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L85 > > This exceeds total timeout set up for remote node startup in > [https://github.com/apache/ignite/blob/282b334f76479460613f28347d8cea97ba23f795/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L1054] > (40 * 1000ms) > > This leads to debug message with ref to remote log file being never shown > because 5 timeout will never be reached > [https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L285] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8534) Upgrade Ignite Spark Module's Spark version to 2.3.0
[ https://issues.apache.org/jira/browse/IGNITE-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482133#comment-16482133 ] Ray commented on IGNITE-8534: - I removed spark-2.10 module because Spark 2.3.0 removed support for scala 2.10 https://issues.apache.org/jira/browse/SPARK-19810 > Upgrade Ignite Spark Module's Spark version to 2.3.0 > > > Key: IGNITE-8534 > URL: https://issues.apache.org/jira/browse/IGNITE-8534 > Project: Ignite > Issue Type: Improvement > Components: spark >Reporter: Ray >Assignee: Ray >Priority: Major > Fix For: 2.6 > > > Spark released its newest version 2.3.0 on Feb 28th, we should upgrade Ignite > Spark module to to the latest version. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8534) Upgrade Ignite Spark Module's Spark version to 2.3.0
[ https://issues.apache.org/jira/browse/IGNITE-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482130#comment-16482130 ] Ray commented on IGNITE-8534: - [~vkulichenko] [~NIzhikov] Please, review my changes. > Upgrade Ignite Spark Module's Spark version to 2.3.0 > > > Key: IGNITE-8534 > URL: https://issues.apache.org/jira/browse/IGNITE-8534 > Project: Ignite > Issue Type: Improvement > Components: spark >Reporter: Ray >Assignee: Ray >Priority: Major > Fix For: 2.6 > > > Spark released its newest version 2.3.0 on Feb 28th, we should upgrade Ignite > Spark module to to the latest version. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8534) Upgrade Ignite Spark Module's Spark version to 2.3.0
[ https://issues.apache.org/jira/browse/IGNITE-8534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482129#comment-16482129 ] ASF GitHub Bot commented on IGNITE-8534: GitHub user ldzhjn opened a pull request: https://github.com/apache/ignite/pull/4033 IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/ldzhjn/ignite ignite-8534 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4033.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 #4033 commit c0a642ff7f550db51a52e10bc9317648a266525c Author: Ray Date: 2018-05-21T02:31:50Z IGNITE-8534 Upgrade Ignite Spark Module's Spark version to 2.3.0 > Upgrade Ignite Spark Module's Spark version to 2.3.0 > > > Key: IGNITE-8534 > URL: https://issues.apache.org/jira/browse/IGNITE-8534 > Project: Ignite > Issue Type: Improvement > Components: spark >Reporter: Ray >Assignee: Ray >Priority: Major > Fix For: 2.6 > > > Spark released its newest version 2.3.0 on Feb 28th, we should upgrade Ignite > Spark module to to the latest version. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8534) Upgrade Ignite Spark Module's Spark version to 2.3.0
Ray created IGNITE-8534: --- Summary: Upgrade Ignite Spark Module's Spark version to 2.3.0 Key: IGNITE-8534 URL: https://issues.apache.org/jira/browse/IGNITE-8534 Project: Ignite Issue Type: Improvement Components: spark Reporter: Ray Assignee: Ray Fix For: 2.6 Spark released its newest version 2.3.0 on Feb 28th, we should upgrade Ignite Spark module to to the latest version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482082#comment-16482082
]
ruchir choudhry commented on IGNITE-8225:
-
Let me take a shot at it, will report back.
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: ruchir choudhry
>Priority: Critical
> Fix For: 2.6
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-8225) Add a command to control script to print current topology version
[
https://issues.apache.org/jira/browse/IGNITE-8225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-8225:
---
Assignee: ruchir choudhry
> Add a command to control script to print current topology version
> -
>
> Key: IGNITE-8225
> URL: https://issues.apache.org/jira/browse/IGNITE-8225
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: ruchir choudhry
>Priority: Critical
> Fix For: 2.6
>
>
> The command should be {{./control.sh --topology}} and should print a short
> summary about the current topology (topology version, number of client nodes,
> number of server nodes, baseline topology information)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-7721:
---
Assignee: ruchir choudhry
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Assignee: ruchir choudhry
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:util="http://www.springframework.org/schema/util"; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-7721:
---
Assignee: ruchir choudhry
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Assignee: ruchir choudhry
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:util="http://www.springframework.org/schema/util"; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482078#comment-16482078
]
ruchir choudhry commented on IGNITE-7721:
-
Can you pls help me with more details:
Is the folder which you are trying to access is having sufficient write
privilege for the problem 01.
for out of memory problem 2: is he env distributed or local
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:util="http://www.springframework.org/schema/util"; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7721) Apache Ignite web session clustering stack after login success
[
https://issues.apache.org/jira/browse/IGNITE-7721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ruchir choudhry reassigned IGNITE-7721:
---
Assignee: (was: ruchir choudhry)
> Apache Ignite web session clustering stack after login success
> --
>
> Key: IGNITE-7721
> URL: https://issues.apache.org/jira/browse/IGNITE-7721
> Project: Ignite
> Issue Type: Bug
> Components: cache, websession
>Affects Versions: 2.3
>Reporter: Sanjeet Jha
>Priority: Blocker
>
> I implement Apache ignite in my OfBiz application. after login my application
> show login susses. but the browser does not get any response from the server.
> Here is my web.xml
>
> {{ IgniteConfigurationFilePath
> specialpurpose/fnp/webapp/fnp/WEB-INF/ignite-config.xml
>
> IgniteWebSessionsCacheName
> replicated
> org.apache.ignite.startup.servlet.ServletContextListenerStartup
>
> IgniteWebSessionsFilter
> org.apache.ignite.cache.websession.WebSessionFilter
>
> IgniteWebSessionsFilter
> /* }}
>
>
>
> {{and my ignite-config.xml}}
>
>
> {{http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:util="http://www.springframework.org/schema/util"; xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd";> id="ignite.cfg" class="org.apache.ignite.configuration.IgniteConfiguration">
>class="org.apache.ignite.configuration.CacheConfiguration">
>
> class="org.apache.ignite.logger.log4j.Log4JLogger"> type="java.lang.String" value="/data/log/ignite-log4j.xml" />
>name="includeEventTypes">static-field="org.apache.ignite.events.EventType.EVT_TASK_STARTED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FINISHED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_FAILED" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_TIMEDOUT" />
> static-field="org.apache.ignite.events.EventType.EVT_TASK_SESSION_ATTR_SET"
> /> static-field="org.apache.ignite.events.EventType.EVT_TASK_REDUCED" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_PUT" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_READ" />
> static-field="org.apache.ignite.events.EventType.EVT_CACHE_OBJECT_REMOVED" />
> class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi"> name="ipFinder"> class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
> 127.0.0.1:47500
> }}{{}}
>
>
>
> I also try to collected ignite log. but there is no error log. Any idea what
> happens.
> And also some time I OutOfMemoryError error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8533) Timeout collision in Client Nodes test suite
[ https://issues.apache.org/jira/browse/IGNITE-8533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482072#comment-16482072 ] Andrew Medvedev commented on IGNITE-8533: - TC: [https://ci.ignite.apache.org/viewLog.html?buildId=1315393&;] I can see one flaky test again there, remote node could not start: [https://ci.ignite.apache.org/viewLog.html?buildId=1315393&buildTypeId=IgniteTests24Java8_StartNodes&tab=buildResultsDiv#testNameId6814497542781613621] not sure if this means that any longer timeout would help (now we have 30sec) Here is clean run on TC https://ci.ignite.apache.org/viewQueued.html?itemId=1315677:0:153 > Timeout collision in Client Nodes test suite > > > Key: IGNITE-8533 > URL: https://issues.apache.org/jira/browse/IGNITE-8533 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Medvedev >Priority: Major > Fix For: 2.6 > > > IGNITE-8085 increased NODE_START_CHECK_LIMIT so "remote" node log is parsed > for longer (set now to 25 * 2000ms) > https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L85 > > This exceeds total timeout set up for remote node startup in > [https://github.com/apache/ignite/blob/282b334f76479460613f28347d8cea97ba23f795/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L1054] > (40 * 1000ms) > > This leads to debug message with ref to remote log file being never shown > because 5 timeout will never be reached > [https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L285] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482069#comment-16482069
]
ruchir choudhry commented on IGNITE-7759:
-
Hello [~guseinov] , [~Sergey Nuyanzin]
Pls review the changes and suggest if i have done the right way,
[http://apache-ignite-developers.2346864.n4.nabble.com/GitHub-ignite-pull-request-4031-IGNITE-7759-gt-Made-changes-for-this-bug-td30706.html]
Regards,
Ruchir
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Assignee: ruchir choudhry
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482068#comment-16482068
]
ASF GitHub Bot commented on IGNITE-7759:
GitHub user ruchirchoudhry opened a pull request:
https://github.com/apache/ignite/pull/4031
IGNITE-7759 --> Made changes for this bug
Hello @gromtech
Pls review it
Thanks,
Ruchir
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ruchirchoudhry/ignite IGNITE-7759
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4031.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 #4031
commit 92294c4a6715ed3465f2a5ebab3cb7eeea2296eb
Author: Ruchir Choudhry
Date: 2018-05-20T22:37:55Z
IGNITE-7759 --> Made changes for this bug
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Assignee: ruchir choudhry
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8085) Flaky failures in Ignite Client Nodes test suite: Remote node could not start.
[
https://issues.apache.org/jira/browse/IGNITE-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482063#comment-16482063
]
Andrew Medvedev commented on IGNITE-8085:
-
[~ivanan.fed]
On closer look 50_000 ms timeout exceeds more general timeout.
I submitted patch in IGNITE-8533 and reopened IGNITE-5883
> Flaky failures in Ignite Client Nodes test suite: Remote node could not
> start.
>
>
> Key: IGNITE-8085
> URL: https://issues.apache.org/jira/browse/IGNITE-8085
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Ivan Fedotov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Ignite Start Nodes
> IgniteStartStopRestartTestSuite:
> IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls (master
> fail rate 12,1%)
> IgniteStartStopRestartTestSuite:
> IgniteProjectionStartStopRestartSelfTest.testStopNodes (master fail rate
> 10,1%)
> IgniteStartStopRestartTestSuite:
> IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds (master fail rate
> 10,1%)
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6814497542781613621&branch=%3Cdefault%3E&tab=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1179745277331816127&branch=%3Cdefault%3E&tab=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-842929918974855010&branch=%3Cdefault%3E&tab=testDetails
> Test itself is quite old. Last commits were from [~tledkov-gridgain] at 2017.
> {noformat}
> class org.apache.ignite.IgniteException: Remote node could not start. See log
> for details:
> /data/teamcity/work/bd85361428dcdb1/work/log/ignite-startNodes/03-29-2018--02-47-24-2003434e.log
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:388)
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:383)
> at
> org.apache.ignite.internal.util.lang.GridFunc.forEach(GridFunc.java:1897)
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls(IgniteProjectionStartStopRestartSelfTest.java:383)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (IGNITE-5883) Ignite Start Nodes test suite is flaky
[ https://issues.apache.org/jira/browse/IGNITE-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Medvedev reopened IGNITE-5883: - Assignee: Andrew Medvedev > Ignite Start Nodes test suite is flaky > -- > > Key: IGNITE-5883 > URL: https://issues.apache.org/jira/browse/IGNITE-5883 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Rakov >Assignee: Andrew Medvedev >Priority: Major > Labels: MakeTeamcityGreenAgain > > Ignite Start Nodes suite contains several flaky tests. > Example runs with sporadic fails: > 1) > http://ci.ignite.apache.org/viewLog.html?buildId=746188&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes > 2) > http://ci.ignite.apache.org/viewLog.html?buildId=747364&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes > The ticket is for investigation and making tests stable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8533) Timeout collision in Client Nodes test suite
[ https://issues.apache.org/jira/browse/IGNITE-8533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482060#comment-16482060 ] ASF GitHub Bot commented on IGNITE-8533: GitHub user andrewmed opened a pull request: https://github.com/apache/ignite/pull/4030 IGNITE-8533 Fix timeout collision in Client Nodes test suite introduc… …ed by IGNITE-8085 You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrewmed/ignite ignite-8533 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4030.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 #4030 commit 212a9fc4d525203e8912775730b61193fde25b9a Author: AMedvedev Date: 2018-05-20T22:07:47Z IGNITE-8533 Fix timeout collision in Client Nodes test suite introduced by IGNITE-8085 > Timeout collision in Client Nodes test suite > > > Key: IGNITE-8533 > URL: https://issues.apache.org/jira/browse/IGNITE-8533 > Project: Ignite > Issue Type: Bug >Reporter: Andrew Medvedev >Priority: Major > Fix For: 2.6 > > > IGNITE-8085 increased NODE_START_CHECK_LIMIT so "remote" node log is parsed > for longer (set now to 25 * 2000ms) > https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L85 > > This exceeds total timeout set up for remote node startup in > [https://github.com/apache/ignite/blob/282b334f76479460613f28347d8cea97ba23f795/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L1054] > (40 * 1000ms) > > This leads to debug message with ref to remote log file being never shown > because 5 timeout will never be reached > [https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L285] > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8533) Timeout collision in Client Nodes test suite
Andrew Medvedev created IGNITE-8533: --- Summary: Timeout collision in Client Nodes test suite Key: IGNITE-8533 URL: https://issues.apache.org/jira/browse/IGNITE-8533 Project: Ignite Issue Type: Bug Reporter: Andrew Medvedev Fix For: 2.6 IGNITE-8085 increased NODE_START_CHECK_LIMIT so "remote" node log is parsed for longer (set now to 25 * 2000ms) https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L85 This exceeds total timeout set up for remote node startup in [https://github.com/apache/ignite/blob/282b334f76479460613f28347d8cea97ba23f795/modules/ssh/src/test/java/org/apache/ignite/internal/IgniteProjectionStartStopRestartSelfTest.java#L1054] (40 * 1000ms) This leads to debug message with ref to remote log file being never shown because 5 timeout will never be reached [https://github.com/apache/ignite/blob/fe6e70e3c8d6a6349ea00b7ec99b215945ffce6d/modules/ssh/src/main/java/org/apache/ignite/internal/util/nodestart/StartNodeCallableImpl.java#L285] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7759) Logger does not print sockTimeout and ackTimeout default values for TcpDiscoverySpi
[
https://issues.apache.org/jira/browse/IGNITE-7759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482036#comment-16482036
]
ruchir choudhry commented on IGNITE-7759:
-
[~Sergey Nuyanzin]: Had to take care of some stuff, will close it asap
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> ---
>
> Key: IGNITE-7759
> URL: https://issues.apache.org/jira/browse/IGNITE-7759
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 1.9, 2.1, 2.3
>Reporter: Roman Guseinov
>Assignee: ruchir choudhry
>Priority: Minor
> Labels: newbie
>
> Logger does not print sockTimeout and ackTimeout default values for
> TcpDiscoverySpi
> Before starting TcpDiscoverySpi logger prints the following message (debug
> mode is enabled):
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=0, ackTimeout=0, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
> Note, that sockTimeout=0 and ackTimeout=0. Default values initializing
> happens after TcpDiscoverySpi.spiStart is called:
> {code:java}
> public class TcpDiscoverySpi extends IgniteSpiAdapter implements DiscoverySpi
> {
> /** Node attribute that is mapped to node's external addresses (value is
> disc.tcp.ext-addrs). */
> /** {@inheritDoc} */
> @Override public void spiStart(@Nullable String igniteInstanceName)
> throws IgniteSpiException {
> initializeImpl();
> }
> /**
> *
> */
> private void initializeImpl() {
> if (impl != null)
> return;
> initFailureDetectionTimeout();
> if (!forceSrvMode &&
> (Boolean.TRUE.equals(ignite.configuration().isClientMode( {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT_CLIENT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT_CLIENT;
> impl = new ClientImpl(this);
> ctxInitLatch.countDown();
> }
> else {
> if (ackTimeout == 0)
> ackTimeout = DFLT_ACK_TIMEOUT;
> if (sockTimeout == 0)
> sockTimeout = DFLT_SOCK_TIMEOUT;
> impl = new ServerImpl(this);
> }
>
> }
> }
> {code}
> To avoid confusion I suggest printing default sockTimeout and ackTimeout if
> they weren't changed like:
> {code:java}
> [main][GridDiscoveryManager] Starting SPI: TcpDiscoverySpi [addrRslvr=null,
> sockTimeout=5000, ackTimeout=5000, marsh=JdkMarshaller
> [clsFilter=org.apache.ignite.internal.IgniteKernal$5@402e37bc], reconCnt=10,
> reconDelay=2000, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5998) Assertion during partition creation in tests
[
https://issues.apache.org/jira/browse/IGNITE-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482007#comment-16482007
]
Andrew Medvedev commented on IGNITE-5998:
-
For these 98.4%
(https://ci.ignite.apache.org/project.html?projectId=IgniteTests20&testNameId=-2922881848812192043&tab=testDetails):
Starting from Dec 18 it is 3 failures out of 182.
Of these 3:
One is with 170 other tests failed, problems on TC agent probable
https://ci.ignite.apache.org/viewLog.html?buildTypeId=IgniteTests20_IgniteQueries2&buildId=1019089
One is "stacktrace unavailable"
https://ci.ignite.apache.org/viewLog.html?buildTypeId=IgniteTests20_IgniteQueries2&buildId=1021552
Only one is with stacktrace
https://ci.ignite.apache.org/viewLog.html?buildTypeId=IgniteTests20_IgniteQueries2&buildId=1133660
but it is NPE, not assertion error as in this ticket, could not reproduce.
When run locally
DynamicIndexReplicatedAtomicConcurrentSelfTest.testQueryConsistencyMultithreaded
is 200/200 success on master
The same on 2.1
> Assertion during partition creation in tests
>
>
> Key: IGNITE-5998
> URL: https://issues.apache.org/jira/browse/IGNITE-5998
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Priority: Critical
> Labels: MakeTeamcityGreenAgain
>
> It was cause of hang of
> DynamicIndexReplicatedAtomicConcurrentSelfTest.testQueryConsistencyMultithreaded
> {code}
> [2017-08-08
> 19:02:01,877][ERROR][exchange-worker-#4300529%index.DynamicIndexReplicatedAtomicConcurrentSelfTest1%][CacheAffinitySharedManager]
> Failed to initialize cache. Will try to rollback cache start routine.
> [cacheName=cache]
> class org.apache.ignite.IgniteCheckedException: Failed to register MBean for
> component:
> org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl@4d0397a2
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.registerMbean(GridCacheProcessor.java:3624)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.createCache(GridCacheProcessor.java:1637)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1863)
> at
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onCacheChangeRequest(CacheAffinitySharedManager.java:742)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onCacheChangeRequest(GridDhtPartitionsExchangeFuture.java:739)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:468)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1954)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: javax.management.InstanceAlreadyExistsException:
> org.apache:clsLdr=6d06d69c,igniteInstanceName=index.DynamicIndexReplicatedAtomicConcurrentSelfTest1,group=cache,name=org.apache.ignite.internal.processors.cache.CacheLocalMetricsMXBeanImpl
> at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1898)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:966)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:900)
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:324)
> at
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at
> org.apache.ignite.internal.util.IgniteUtils.registerCacheMBean(IgniteUtils.java:4574)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.registerMbean(GridCacheProcessor.java:3620)
> ... 8 more
> [2017-08-08
> 19:02:01,878][ERROR][exchange-worker-#4300529%index.DynamicIndexReplicatedAtomicConcurrentSelfTest1%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=4,
> minorTopVer=1], discoEvt=DiscoveryCustomEvent
> [customMsg=DynamicCacheChangeBatch
> [id=2490c129e51-bbb352cc-e911-41e1-afd6-67e8ed91809c,
> reqs=[DynamicCacheChangeRequest [cacheName=cache, hasCfg=true,
> nodeId=fdc8ffc4-3da3-470e-a8ac-5f8b4204, clientStartOnly=false,
> stop=false, destroy=false]], exchangeActions=E
[jira] [Commented] (IGNITE-8469) Non-heap memroy leak for calling cluster activation multi times
[
https://issues.apache.org/jira/browse/IGNITE-8469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481997#comment-16481997
]
Maxim Muzafarov commented on IGNITE-8469:
-
[~dpavlov]
TC ready, Run :: All look good: [#1747 (19 May 18
16:43)|https://ci.ignite.apache.org/viewLog.html?buildId=1313087&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll]
I've also rerun some suspicious suites:
Activate | Deactivate Cluster [#976 (19 May 18
18:04)|https://ci.ignite.apache.org/viewLog.html?buildId=1313106&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_ActivateDeactivateCluster]
Run :: PDS [#1786 (20 May 18
13:19)|https://ci.ignite.apache.org/viewLog.html?buildId=1314160&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAllPds]
Data Structures [#805 (20 May 18
13:38)|https://ci.ignite.apache.org/viewLog.html?buildId=1314206&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_DataStructures]
But I can't get clear build without execution timeouts and snapshot dependency
fails.
> Non-heap memroy leak for calling cluster activation multi times
> ---
>
> Key: IGNITE-8469
> URL: https://issues.apache.org/jira/browse/IGNITE-8469
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.6
>
>
> Calling multiple time cluster (with enabled persistence and started client
> nodes) activation {{ig3CB.cluster().active(true);}} leads to non-heap memory
> leak.
> Line
> {{org/apache/ignite/internal/pagemem/impl/PageMemoryNoStoreImpl.java:234}}
> looks suspicious because of in case method
> {{org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl#start}}
> callled multi times (e.g. activate(true) called multi times) we lost info
> about allocated regions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8436) Executor service for services does not shutdown properly
[
https://issues.apache.org/jira/browse/IGNITE-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481934#comment-16481934
]
Maxim Muzafarov commented on IGNITE-8436:
-
[~prabhat],
I've left some comments in your PR.
Please, also refer to this one page –
[https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-ReviewWithUpsource]
More easier way for review is to create Upsorce branch review there. Can you do
it?
> Executor service for services does not shutdown properly
>
>
> Key: IGNITE-8436
> URL: https://issues.apache.org/jira/browse/IGNITE-8436
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Reporter: Maxim Muzafarov
>Assignee: Prabhat Ranjan
>Priority: Major
> Labels: newbie
> Fix For: 2.6
>
>
> Issue [IGNITE-4802|https://issues.apache.org/jira/browse/IGNITE-4802]
> introduces us separete thread pool for services execution.
> {{IgniteEx}} class defines a factory for the main Ignite API. It controls
> Grid life cycle and allows listening for grid events.
> As cotributor, you should ensure that execution pool shutdowns properly and
> provide fix if needed in case stop grid instance method call occurs.
> {code:java|title=IgniteEx.java|borderStyle=solid}
> /** Executor service for services. */
> private ThreadPoolExecutor svcExecSvc;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-5883) Ignite Start Nodes test suite is flaky
[ https://issues.apache.org/jira/browse/IGNITE-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481897#comment-16481897 ] Andrew Medvedev commented on IGNITE-5883: - Resolved in IGNITE-8085 > Ignite Start Nodes test suite is flaky > -- > > Key: IGNITE-5883 > URL: https://issues.apache.org/jira/browse/IGNITE-5883 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Rakov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Ignite Start Nodes suite contains several flaky tests. > Example runs with sporadic fails: > 1) > http://ci.ignite.apache.org/viewLog.html?buildId=746188&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes > 2) > http://ci.ignite.apache.org/viewLog.html?buildId=747364&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes > The ticket is for investigation and making tests stable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8085) Flaky failures in Ignite Client Nodes test suite: Remote node could not start.
[
https://issues.apache.org/jira/browse/IGNITE-8085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481895#comment-16481895
]
Andrew Medvedev commented on IGNITE-8085:
-
Re IGNITE-5883:
Yes, failures there were of the same reason: remote node could not start
As it is fixed now, I set IGNITE-5883 to duplicate.
Thanks [~ivanan.fed] for pinning this down
> Flaky failures in Ignite Client Nodes test suite: Remote node could not
> start.
>
>
> Key: IGNITE-8085
> URL: https://issues.apache.org/jira/browse/IGNITE-8085
> Project: Ignite
> Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Ivan Fedotov
>Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Ignite Start Nodes
> IgniteStartStopRestartTestSuite:
> IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls (master
> fail rate 12,1%)
> IgniteStartStopRestartTestSuite:
> IgniteProjectionStartStopRestartSelfTest.testStopNodes (master fail rate
> 10,1%)
> IgniteStartStopRestartTestSuite:
> IgniteProjectionStartStopRestartSelfTest.testStopNodesByIds (master fail rate
> 10,1%)
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=6814497542781613621&branch=%3Cdefault%3E&tab=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=1179745277331816127&branch=%3Cdefault%3E&tab=testDetails
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-842929918974855010&branch=%3Cdefault%3E&tab=testDetails
> Test itself is quite old. Last commits were from [~tledkov-gridgain] at 2017.
> {noformat}
> class org.apache.ignite.IgniteException: Remote node could not start. See log
> for details:
> /data/teamcity/work/bd85361428dcdb1/work/log/ignite-startNodes/03-29-2018--02-47-24-2003434e.log
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:388)
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest$7.apply(IgniteProjectionStartStopRestartSelfTest.java:383)
> at
> org.apache.ignite.internal.util.lang.GridFunc.forEach(GridFunc.java:1897)
> at
> org.apache.ignite.internal.IgniteProjectionStartStopRestartSelfTest.testStartFiveNodesInTwoCalls(IgniteProjectionStartStopRestartSelfTest.java:383)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2002)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
> at
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1917)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (IGNITE-5883) Ignite Start Nodes test suite is flaky
[ https://issues.apache.org/jira/browse/IGNITE-5883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Medvedev resolved IGNITE-5883. - Resolution: Duplicate > Ignite Start Nodes test suite is flaky > -- > > Key: IGNITE-5883 > URL: https://issues.apache.org/jira/browse/IGNITE-5883 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Rakov >Priority: Major > Labels: MakeTeamcityGreenAgain > > Ignite Start Nodes suite contains several flaky tests. > Example runs with sporadic fails: > 1) > http://ci.ignite.apache.org/viewLog.html?buildId=746188&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes > 2) > http://ci.ignite.apache.org/viewLog.html?buildId=747364&tab=buildResultsDiv&buildTypeId=Ignite20Tests_IgniteStartNodes > The ticket is for investigation and making tests stable. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8436) Executor service for services does not shutdown properly
[
https://issues.apache.org/jira/browse/IGNITE-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481854#comment-16481854
]
Prabhat Ranjan commented on IGNITE-8436:
Thanks [~vkulichenko].
I have added test to check all executors are terminated (
[https://ci.ignite.apache.org/viewLog.html?buildId=1314045&buildTypeId=IgniteTests24Java8_Basic1&tab=testsInfo]
)
Please review [https://github.com/apache/ignite/pull/3945]
> Executor service for services does not shutdown properly
>
>
> Key: IGNITE-8436
> URL: https://issues.apache.org/jira/browse/IGNITE-8436
> Project: Ignite
> Issue Type: Bug
> Components: managed services
>Reporter: Maxim Muzafarov
>Assignee: Prabhat Ranjan
>Priority: Major
> Labels: newbie
> Fix For: 2.6
>
>
> Issue [IGNITE-4802|https://issues.apache.org/jira/browse/IGNITE-4802]
> introduces us separete thread pool for services execution.
> {{IgniteEx}} class defines a factory for the main Ignite API. It controls
> Grid life cycle and allows listening for grid events.
> As cotributor, you should ensure that execution pool shutdowns properly and
> provide fix if needed in case stop grid instance method call occurs.
> {code:java|title=IgniteEx.java|borderStyle=solid}
> /** Executor service for services. */
> private ThreadPoolExecutor svcExecSvc;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
