[jira] [Commented] (IGNITE-9893) add hibernate-5.2 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671134#comment-16671134 ] Scott Feldstein commented on IGNITE-9893: - Updated the code to fix the compilation issue. As I commented on the pull request, I'm seeing flakey tests on HibernateL2CacheTransactionSelfTest.testQueryCache(). The statistics Hit, Miss and Put count are not always in sync. > add hibernate-5.2 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Assignee: Scott Feldstein >Priority: Major > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-7926) Web console: demo faled to start under java >= 9
[ https://issues.apache.org/jira/browse/IGNITE-7926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Novikov reassigned IGNITE-7926: -- Assignee: Vasiliy Sisko (was: Ilya Murchenko) > Web console: demo faled to start under java >= 9 > > > Key: IGNITE-7926 > URL: https://issues.apache.org/jira/browse/IGNITE-7926 > Project: Ignite > Issue Type: Bug > Components: wizards >Affects Versions: 2.4 >Reporter: Pavel Konstantinov >Assignee: Vasiliy Sisko >Priority: Minor > Fix For: 2.7 > > > We need to add support for Java 9 to web console demo. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671106#comment-16671106
]
Nikolay Izhikov commented on IGNITE-9312:
-
Hello, [~PetrovMikhail]
1.
https://github.com/apache/ignite/pull/4632/files#diff-14b348bc73c7a35c2edb842a68ac5445R290
- is this merge error? Seems, this changes doesn't relate to current PR
2. Let's enable an inspection to check unnecessary @SuppressWarnings in
TeamCity settings. This should be included in current PR.
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (IGNITE-9010) Move web-console build to dedicated root directory
[
https://issues.apache.org/jira/browse/IGNITE-9010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Novikov closed IGNITE-9010.
--
> Move web-console build to dedicated root directory
> --
>
> Key: IGNITE-9010
> URL: https://issues.apache.org/jira/browse/IGNITE-9010
> Project: Ignite
> Issue Type: Task
>Reporter: Peter Ivanov
>Assignee: Ilya Murchenko
>Priority: Major
> Fix For: 2.8
>
>
> # Move web-console docker image build (web-console, frontend and backend) to
> {{/docker}} directory.
> # Prepare README.md file in root of {{/docker}} directory with instructions
> on how to build corresponding image. Remove obsolete per-image README's from
> Dockerfile directories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10100) No public Java API to call Ignite.NET service
Alexey Kukushkin created IGNITE-10100: - Summary: No public Java API to call Ignite.NET service Key: IGNITE-10100 URL: https://issues.apache.org/jira/browse/IGNITE-10100 Project: Ignite Issue Type: Improvement Components: platforms Affects Versions: 2.6 Reporter: Alexey Kukushkin Assignee: Alexey Kukushkin Ignite wraps .NET services in PlatformDotNetServiceImpl implementing PlatformService interface. To call a .NET service from a Java client I have to use invokeMethod API defined in PlatformService interface. The problem is for some reason PlatformService is defined in internal Ignite package apache.ignite.internal.processors.platform.services. This API must be public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670815#comment-16670815
]
ASF GitHub Bot commented on IGNITE-9849:
dspavlov commented on a change in pull request #57: IGNITE-9849 Refactor Master
trends
URL: https://github.com/apache/ignite-teamcity-bot/pull/57#discussion_r229881457
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/buildcondition/BuildConditionDao.java
##
@@ -15,18 +15,19 @@
* limitations under the License.
*/
-package org.apache.ignite.ci.tcbot.condition;
+package org.apache.ignite.ci.teamcity.ignited.buildcondition;
import javax.inject.Inject;
import javax.inject.Provider;
import org.apache.ignite.Ignite;
import org.apache.ignite.IgniteCache;
-import org.apache.ignite.ci.db.TcHelperDb;
import org.apache.ignite.ci.teamcity.ignited.IStringCompactor;
+import static
org.apache.ignite.ci.teamcity.ignited.IgniteStringCompactor.getCache8PartsConfig;
+
public class BuildConditionDao {
/** Cache name*/
-public static final String BUILD_CONDITIONS_CACHE_NAME = "buildConditions";
+public static final String BUILDS_CONDITIONS_CACHE_NAME =
"buildsConditions";
Review comment:
We should add old cache name removal in DbMigrations class. Fewer caches we
have, faster the bot start is.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove invalid builds from the selection
>
>
> Key: IGNITE-9849
> URL: https://issues.apache.org/jira/browse/IGNITE-9849
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> In selection sometimes there are builds with abnormal values. For example,
> the average number of failed tests is 25. But in the build [1953935] there
> are 2939 failed tests. This is an anomalous value. Need to add the ability to
> remove it from the selection. Build [1953935] - not valid.
> In total,
> 1. While clicking on a point on the chart, show a button that allows marking
> a build invalid and excludes it from further selections.
> 2. Reduce the number of erroneous exceptions. Compare the value with the
> average, if the difference is small - ask for confirmation of the operation.
> 3. Add the ability to return an excluded build to the selection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670813#comment-16670813
]
ASF GitHub Bot commented on IGNITE-9849:
dspavlov commented on a change in pull request #57: IGNITE-9849 Refactor Master
trends
URL: https://github.com/apache/ignite-teamcity-bot/pull/57#discussion_r229880842
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/hist/BuildsHistory.java
##
@@ -92,25 +91,26 @@
/** */
public void initialize(ICredentialsProv prov, ServletContext context) {
-if (!prov.hasAccess(srvId))
-throw ServiceUnauthorizedException.noCreds(srvId);
+final IStringCompactor compactor =
CtxListener.getInjector(context).getInstance(IStringCompactor.class);
ITcHelper tcHelper = CtxListener.getTcHelper(context);
-IAnalyticsEnabledTeamcity teamcity = tcHelper.server(srvId, prov);
+ITeamcity teamcity = tcHelper.server(srvId, prov);
ITeamcityIgnitedProvider tcIgnitedProv =
CtxListener.getInjector(context)
.getInstance(ITeamcityIgnitedProvider.class);
-ITeamcityIgnited ignited = tcIgnitedProv.server(srvId, prov);
+ITeamcityIgnited ignitedTeamcity = tcIgnitedProv.server(srvId, prov);
-int[] finishedBuildsIds =
teamcity.getBuildNumbersFromHistory(buildTypeId, branchName,
-sinceDateFilter, untilDateFilter);
+List finishedBuildsIds = ignitedTeamcity
+.getFinishedBuildsCompacted(buildTypeId, branchName,
sinceDateFilter, untilDateFilter)
Review comment:
Probably we need filter out canceled builds here. New method may return
finished build, but having status Unknown. It may mean build was canceled.
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove invalid builds from the selection
>
>
> Key: IGNITE-9849
> URL: https://issues.apache.org/jira/browse/IGNITE-9849
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> In selection sometimes there are builds with abnormal values. For example,
> the average number of failed tests is 25. But in the build [1953935] there
> are 2939 failed tests. This is an anomalous value. Need to add the ability to
> remove it from the selection. Build [1953935] - not valid.
> In total,
> 1. While clicking on a point on the chart, show a button that allows marking
> a build invalid and excludes it from further selections.
> 2. Reduce the number of erroneous exceptions. Compare the value with the
> average, if the difference is small - ask for confirmation of the operation.
> 3. Add the ability to return an excluded build to the selection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670809#comment-16670809
]
ASF GitHub Bot commented on IGNITE-9849:
dspavlov commented on a change in pull request #57: IGNITE-9849 Refactor Master
trends
URL: https://github.com/apache/ignite-teamcity-bot/pull/57#discussion_r229880064
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -91,122 +96,122 @@ public BuildStatisticsSummary(Integer buildId){
}
/** Initialize build statistics. */
-public void initialize(@Nonnull final ITeamcity teamcity) {
-Build build = teamcity.getBuild(buildId);
+public void initialize(@Nonnull final IStringCompactor compactor, @Nonnull
final ITeamcityIgnited ignitedTeamcity) {
+if (strIds.isEmpty()) {
+strIds.put(STATUS_SUCCESS, compactor.getStringId(STATUS_SUCCESS));
+strIds.put(TC_EXIT_CODE, compactor.getStringId(TC_EXIT_CODE));
+strIds.put(TC_OOME, compactor.getStringId(TC_OOME));
+strIds.put(TC_JVM_CRASH, compactor.getStringId(TC_JVM_CRASH));
+strIds.put(TC_EXECUTION_TIMEOUT,
compactor.getStringId(TC_EXECUTION_TIMEOUT));
+}
+
+FatBuildCompacted build = ignitedTeamcity.getFatBuild(buildId);
isFakeStub = build.isFakeStub();
if (isFakeStub)
return;
DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
-dateFormat.format(build.getFinishDate());
+
startDate = dateFormat.format(build.getStartDate());
-testOccurrences = build.testOccurrences;
+int[] arr = new int[4];
-duration = (build.getFinishDate().getTime() -
build.getStartDate().getTime()) / 1000;
+build.getAllTests().forEach(t -> {
+if (t.getIgnoredFlag())
+arr[0]++;
+else if (t.getMutedFlag())
+arr[1]++;
+else if (t.status() != strIds.get(STATUS_SUCCESS))
+arr[2]++;
-List snapshotDependencies =
getSnapshotDependencies(teamcity, build);
+arr[3]++;
+});
-List snapshotDependenciesWithProblems =
getBuildsWithProblems(snapshotDependencies);
+testOccurrences.ignored = arr[0];
+testOccurrences.muted = arr[1];
+testOccurrences.failed = arr[2];
+testOccurrences.count = arr[3];
+testOccurrences.passed = testOccurrences.count -
testOccurrences.failed - testOccurrences.ignored -
+testOccurrences.muted;
-problemOccurrenceList = getProblems(teamcity,
snapshotDependenciesWithProblems);
+duration = (build.getFinishDate().getTime() -
build.getStartDate().getTime()) / 1000;
-totalProblems = getRes();
-}
+List snapshotDependencies =
getSnapshotDependencies(ignitedTeamcity, buildId);
-private long getExecutionTimeoutCount(String buildTypeId) {
-return
getProblemsStream(buildTypeId).filter(ProblemOccurrence::isExecutionTimeout).count();
-}
+List snapshotDependenciesWithProblems =
getBuildsWithProblems(snapshotDependencies);
-private long getJvmCrashProblemCount(String buildTypeId) {
-return
getProblemsStream(buildTypeId).filter(ProblemOccurrence::isJvmCrash).count();
-}
+problemOccurrenceList = getProblems(snapshotDependenciesWithProblems);
-private long getExitCodeProblemsCount(String buildTypeId) {
-return
getProblemsStream(buildTypeId).filter(ProblemOccurrence::isExitCode).count();
+totalProblems = getBuildTypeProblemsCount();
}
-private long getOomeProblemCount(String buildTypeId) {
-return
getProblemsStream(buildTypeId).filter(ProblemOccurrence::isOome).count();
+/**
+ * @param problemName Problem name.
+ */
+private long getProblemsCount(String problemName) {
+if (problemOccurrenceList == null)
+return 0;
+
+return problemOccurrenceList.stream()
+.filter(Objects::nonNull)
+.filter(p -> p.type() == strIds.get(problemName)).count();
}
/**
* Problems for all snapshot-dependencies.
*
- * @param teamcity Teamcity.
+ * @param builds Builds.
*/
-private List getProblems(@Nonnull final ITeamcity
teamcity, List builds){
-List problemOccurrences = new ArrayList<>();
+private List getProblems(List builds){
+List problemOccurrences = new ArrayList<>();
-for (BuildRef buildRef : builds)
-problemOccurrences.addAll(teamcity
-.getProblems(buildRef)
-.getProblemsNonNull());
+for (FatBuildCompacted build : builds)
+problemOccurrences.addAll(
+build.problems()
+);
return
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670807#comment-16670807
]
ASF GitHub Bot commented on IGNITE-9849:
dspavlov commented on a change in pull request #57: IGNITE-9849 Refactor Master
trends
URL: https://github.com/apache/ignite-teamcity-bot/pull/57#discussion_r229879687
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -91,122 +96,122 @@ public BuildStatisticsSummary(Integer buildId){
}
/** Initialize build statistics. */
-public void initialize(@Nonnull final ITeamcity teamcity) {
-Build build = teamcity.getBuild(buildId);
+public void initialize(@Nonnull final IStringCompactor compactor, @Nonnull
final ITeamcityIgnited ignitedTeamcity) {
+if (strIds.isEmpty()) {
+strIds.put(STATUS_SUCCESS, compactor.getStringId(STATUS_SUCCESS));
+strIds.put(TC_EXIT_CODE, compactor.getStringId(TC_EXIT_CODE));
+strIds.put(TC_OOME, compactor.getStringId(TC_OOME));
+strIds.put(TC_JVM_CRASH, compactor.getStringId(TC_JVM_CRASH));
+strIds.put(TC_EXECUTION_TIMEOUT,
compactor.getStringId(TC_EXECUTION_TIMEOUT));
+}
+
+FatBuildCompacted build = ignitedTeamcity.getFatBuild(buildId);
isFakeStub = build.isFakeStub();
if (isFakeStub)
return;
DateFormat dateFormat = new SimpleDateFormat("dd-MM-'T'HH:mm:ss");
-dateFormat.format(build.getFinishDate());
+
startDate = dateFormat.format(build.getStartDate());
-testOccurrences = build.testOccurrences;
+int[] arr = new int[4];
-duration = (build.getFinishDate().getTime() -
build.getStartDate().getTime()) / 1000;
+build.getAllTests().forEach(t -> {
+if (t.getIgnoredFlag())
+arr[0]++;
+else if (t.getMutedFlag())
+arr[1]++;
+else if (t.status() != strIds.get(STATUS_SUCCESS))
+arr[2]++;
-List snapshotDependencies =
getSnapshotDependencies(teamcity, build);
+arr[3]++;
+});
-List snapshotDependenciesWithProblems =
getBuildsWithProblems(snapshotDependencies);
+testOccurrences.ignored = arr[0];
+testOccurrences.muted = arr[1];
+testOccurrences.failed = arr[2];
+testOccurrences.count = arr[3];
+testOccurrences.passed = testOccurrences.count -
testOccurrences.failed - testOccurrences.ignored -
+testOccurrences.muted;
-problemOccurrenceList = getProblems(teamcity,
snapshotDependenciesWithProblems);
+duration = (build.getFinishDate().getTime() -
build.getStartDate().getTime()) / 1000;
Review comment:
Just as an option: we can take build duration from the build statistics, it
is always provided with new FatBuild
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove invalid builds from the selection
>
>
> Key: IGNITE-9849
> URL: https://issues.apache.org/jira/browse/IGNITE-9849
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> In selection sometimes there are builds with abnormal values. For example,
> the average number of failed tests is 25. But in the build [1953935] there
> are 2939 failed tests. This is an anomalous value. Need to add the ability to
> remove it from the selection. Build [1953935] - not valid.
> In total,
> 1. While clicking on a point on the chart, show a button that allows marking
> a build invalid and excludes it from further selections.
> 2. Reduce the number of erroneous exceptions. Compare the value with the
> average, if the difference is small - ask for confirmation of the operation.
> 3. Add the ability to return an excluded build to the selection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[ https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670805#comment-16670805 ] ASF GitHub Bot commented on IGNITE-9849: dspavlov commented on a change in pull request #57: IGNITE-9849 Refactor Master trends URL: https://github.com/apache/ignite-teamcity-bot/pull/57#discussion_r229879186 ## File path: ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java ## @@ -66,10 +71,10 @@ public String startDate; /** Test occurrences. */ -public TestOccurrencesRef testOccurrences; +public TestOccurrencesRef testOccurrences = new TestOccurrencesRef();; Review comment: ;; - can remove one This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove invalid builds from the selection > > > Key: IGNITE-9849 > URL: https://issues.apache.org/jira/browse/IGNITE-9849 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > In selection sometimes there are builds with abnormal values. For example, > the average number of failed tests is 25. But in the build [1953935] there > are 2939 failed tests. This is an anomalous value. Need to add the ability to > remove it from the selection. Build [1953935] - not valid. > In total, > 1. While clicking on a point on the chart, show a button that allows marking > a build invalid and excludes it from further selections. > 2. Reduce the number of erroneous exceptions. Compare the value with the > average, if the difference is small - ask for confirmation of the operation. > 3. Add the ability to return an excluded build to the selection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670806#comment-16670806
]
ASF GitHub Bot commented on IGNITE-9849:
dspavlov commented on a change in pull request #57: IGNITE-9849 Refactor Master
trends
URL: https://github.com/apache/ignite-teamcity-bot/pull/57#discussion_r229879300
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/web/model/current/BuildStatisticsSummary.java
##
@@ -52,8 +57,8 @@
static {
shortProblemNames.put(TOTAL, "TT");
shortProblemNames.put(ProblemOccurrence.TC_EXECUTION_TIMEOUT, "ET");
Review comment:
We can replace reference to class because of static import
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove invalid builds from the selection
>
>
> Key: IGNITE-9849
> URL: https://issues.apache.org/jira/browse/IGNITE-9849
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> In selection sometimes there are builds with abnormal values. For example,
> the average number of failed tests is 25. But in the build [1953935] there
> are 2939 failed tests. This is an anomalous value. Need to add the ability to
> remove it from the selection. Build [1953935] - not valid.
> In total,
> 1. While clicking on a point on the chart, show a button that allows marking
> a build invalid and excludes it from further selections.
> 2. Reduce the number of erroneous exceptions. Compare the value with the
> average, if the difference is small - ask for confirmation of the operation.
> 3. Add the ability to return an excluded build to the selection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[
https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670803#comment-16670803
]
ASF GitHub Bot commented on IGNITE-9849:
dspavlov commented on a change in pull request #57: IGNITE-9849 Refactor Master
trends
URL: https://github.com/apache/ignite-teamcity-bot/pull/57#discussion_r229878447
##
File path:
ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/teamcity/ignited/TeamcityIgnitedImpl.java
##
@@ -116,6 +119,142 @@ private String taskName(String taskName) {
return conn.host();
}
+/** {@inheritDoc} */
+public List getFinishedBuildsCompacted(
+@Nullable String buildTypeId,
+@Nullable String branchName,
+@Nullable Date sinceDate,
+@Nullable Date untilDate) {
+int unknownStatus = compactor.getStringId(STATUS_UNKNOWN);
+
+List buildRefs =
getBuildHistoryCompacted(buildTypeId, branchName)
+.stream().filter(b -> b.status() !=
unknownStatus).collect(Collectors.toList());
+
+int idSince = 0;
+int idUntil = buildRefs.size() - 1;
+
+if (sinceDate != null) {
+idSince = binarySearchDate(buildRefs, 0, buildRefs.size(),
sinceDate, true);
+idSince = idSince == -2 ? 0 : idSince;
Review comment:
To avoid magic numbers like -1, -2, -3 I can suggest introducing a constants
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Remove invalid builds from the selection
>
>
> Key: IGNITE-9849
> URL: https://issues.apache.org/jira/browse/IGNITE-9849
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> In selection sometimes there are builds with abnormal values. For example,
> the average number of failed tests is 25. But in the build [1953935] there
> are 2939 failed tests. This is an anomalous value. Need to add the ability to
> remove it from the selection. Build [1953935] - not valid.
> In total,
> 1. While clicking on a point on the chart, show a button that allows marking
> a build invalid and excludes it from further selections.
> 2. Reduce the number of erroneous exceptions. Compare the value with the
> average, if the difference is small - ask for confirmation of the operation.
> 3. Add the ability to return an excluded build to the selection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9557) Assert exception on explain of DELETE query.
[
https://issues.apache.org/jira/browse/IGNITE-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670689#comment-16670689
]
Pavel Kuznetsov commented on IGNITE-9557:
-
Updated PR.
test run : https://ci.ignite.apache.org/viewQueued.html?itemId=2213784
> Assert exception on explain of DELETE query.
>
>
> Key: IGNITE-9557
> URL: https://issues.apache.org/jira/browse/IGNITE-9557
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Vasiliy Sisko
>Assignee: Pavel Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>
> On execution of an query:
> {code:java}
> explain delete from "schema".type {code}
> received exception:
> {code:java}
> java.lang.AssertionError
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.parseAndSplit(IgniteH2Indexing.java:2309)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2105)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2139)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2134)
> at
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2711)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2148)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2083)
> at
> org.apache.ignite.internal.visor.query.VisorQueryTask$VisorQueryJob.run(VisorQueryTask.java:94)
> at
> org.apache.ignite.internal.visor.query.VisorQueryTask$VisorQueryJob.run(VisorQueryTask.java:59)
> at org.apache.ignite.internal.visor.VisorJob.execute(VisorJob.java:69)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6765)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1125)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1420)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:666)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:538)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:764)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:509)
> at
> org.apache.ignite.internal.IgniteComputeImpl.executeAsync0(IgniteComputeImpl.java:488)
> at
> org.apache.ignite.internal.IgniteComputeImpl.executeAsync(IgniteComputeImpl.java:468)
> at
> org.apache.ignite.internal.visor.compute.VisorGatewayTask$VisorGatewayJob.execute(VisorGatewayTask.java:462)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
> at
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6765)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
> at
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1125)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.sendRequest(GridTaskWorker.java:1420)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.processMappedJobs(GridTaskWorker.java:666)
> at
> org.apache.ignite.internal.processors.task.GridTaskWorker.body(GridTaskWorker.java:538)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:764)
> at
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:509)
> at
>
[jira] [Commented] (IGNITE-9849) Remove invalid builds from the selection
[ https://issues.apache.org/jira/browse/IGNITE-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670662#comment-16670662 ] ASF GitHub Bot commented on IGNITE-9849: zzzadruga opened a new pull request #57: IGNITE-9849 Refactor Master trends URL: https://github.com/apache/ignite-teamcity-bot/pull/57 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Remove invalid builds from the selection > > > Key: IGNITE-9849 > URL: https://issues.apache.org/jira/browse/IGNITE-9849 > Project: Ignite > Issue Type: Sub-task >Reporter: Nikolai Kulagin >Assignee: Nikolai Kulagin >Priority: Minor > > In selection sometimes there are builds with abnormal values. For example, > the average number of failed tests is 25. But in the build [1953935] there > are 2939 failed tests. This is an anomalous value. Need to add the ability to > remove it from the selection. Build [1953935] - not valid. > In total, > 1. While clicking on a point on the chart, show a button that allows marking > a build invalid and excludes it from further selections. > 2. Reduce the number of erroneous exceptions. Compare the value with the > average, if the difference is small - ask for confirmation of the operation. > 3. Add the ability to return an excluded build to the selection. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8010) Validate marshaller mappings on join
[ https://issues.apache.org/jira/browse/IGNITE-8010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670632#comment-16670632 ] ASF GitHub Bot commented on IGNITE-8010: GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/5228 IGNITE-8010 Validate marshaller mappings on join. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8010 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5228.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 #5228 commit e2b42fdf308a13fa17b9e543261129666825d986 Author: Denis Mekhanikov Date: 2018-10-31T19:35:41Z IGNITE-8010 Validate marshaller mappings on join. > Validate marshaller mappings on join > > > Key: IGNITE-8010 > URL: https://issues.apache.org/jira/browse/IGNITE-8010 > Project: Ignite > Issue Type: Improvement >Reporter: Denis Mekhanikov >Assignee: Denis Mekhanikov >Priority: Major > Fix For: 2.8 > > > When a new node joins topology, it sends its marshaller mappings in a > discovery join message. > Additional validation should be implemented to make nodes with conflicting > marshaller mappings be rejected from connecting to the cluster. > Such procedure is already implemented for binary metadata. Marshaller > mappings should be validated in a similar way. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9607) Service Grid redesign - phase 1
[ https://issues.apache.org/jira/browse/IGNITE-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670562#comment-16670562 ] Vyacheslav Daradur commented on IGNITE-9607: Looks like this failures don't relate to PR changes, according to build logs of failures tests. Also couldn't reproduce locally. Rerun TC just to be sure. > Service Grid redesign - phase 1 > --- > > Key: IGNITE-9607 > URL: https://issues.apache.org/jira/browse/IGNITE-9607 > Project: Ignite > Issue Type: Improvement > Components: managed services >Reporter: Vyacheslav Daradur >Assignee: Vyacheslav Daradur >Priority: Major > Fix For: 2.8 > > > This is an umbrella ticket for tasks which should be implemented atomically > in phase #1 of Service Grid redesign. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9607) Service Grid redesign - phase 1
[
https://issues.apache.org/jira/browse/IGNITE-9607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670558#comment-16670558
]
Ignite TC Bot commented on IGNITE-9607:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Direct IO) 2{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2210964]]
*
WalDeletionArchiveFsyncTest.testGridDoesNotStart_BecauseBothWalHistorySizeAndMaxWalArchiveSizeUsed
(last started)
{color:#d04437}Queries (Binary Objects Simple Mapper){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2210978]]
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
IgniteSqlSplitterSelfTest.testReplicatedTablesUsingPartitionedCacheSegmentedClient
- 0,0% fails in last 100 master runs.
* IgniteBinarySimpleNameMapperCacheQueryTestSuite:
OptimizedMarshallerIndexNameTest.testOptimizedMarshallerIndex - 0,0% fails in
last 100 master runs.
{color:#d04437}Queries 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2210979]]
* IgniteBinaryCacheQueryTestSuite:
OptimizedMarshallerIndexNameTest.testOptimizedMarshallerIndex - 0,0% fails in
last 100 master runs.
{color:#d04437}Platform C++ (Windows x64){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2210921]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 100 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 100 master runs.
{color:#d04437}Platform C++ (Linux){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2210920]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 100 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 100 master runs.
{color:#d04437}Platform C++ (Linux Clang){color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2210927]]
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsSelectMerge2 - 0,0% fails in
last 100 master runs.
* IgniteOdbcTest: QueriesTestSuite: TestManyCursorsTwoSelects2 - 0,0% fails in
last 100 master runs.
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2210984buildTypeId=IgniteTests24Java8_RunAll]
> Service Grid redesign - phase 1
> ---
>
> Key: IGNITE-9607
> URL: https://issues.apache.org/jira/browse/IGNITE-9607
> Project: Ignite
> Issue Type: Improvement
> Components: managed services
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>Priority: Major
> Fix For: 2.8
>
>
> This is an umbrella ticket for tasks which should be implemented atomically
> in phase #1 of Service Grid redesign.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670555#comment-16670555 ] ASF GitHub Bot commented on IGNITE-10099: - Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5226 > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Assignee: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10091) [TC Bot] Replace PR source for autocompleting branch fields
[ https://issues.apache.org/jira/browse/IGNITE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670536#comment-16670536 ] Dmitriy Pavlov commented on IGNITE-10091: - [~SomeFire] thank you for the contribution! > [TC Bot] Replace PR source for autocompleting branch fields > --- > > Key: IGNITE-10091 > URL: https://issues.apache.org/jira/browse/IGNITE-10091 > Project: Ignite > Issue Type: Task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > > Currently, client receive PRs info for autocompletion list separately from > the server. Instead, we should get this info from the Bot, because it is > cached here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8896) Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()
[
https://issues.apache.org/jira/browse/IGNITE-8896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670534#comment-16670534
]
Dmitriy Pavlov commented on IGNITE-8896:
[~RodionVl], Please set the status to patch available once you're sure the fix
is ready
> Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()
> ---
>
> Key: IGNITE-8896
> URL: https://issues.apache.org/jira/browse/IGNITE-8896
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Karachentsev
>Assignee: Rodion
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Javadoc for TcpCommunicationSpi.setSlowClientQueueLimit() says that is should
> be set to value equal to TcpCommunicationSpi.getMessageQueueLimit().
> But this is wrong, because first checks back pressure limit and sender thread
> will be blocked before slow client check. Also, warning checks the value
> correctly, but message should be "...greater or equal...":
> {code:java}
> if (slowClientQueueLimit > 0 && msgQueueLimit > 0 && slowClientQueueLimit >=
> msgQueueLimit) {
> U.quietAndWarn(log, "Slow client queue limit is set to a value
> greater than message queue limit " +
> "(slow client queue limit will have no effect)
> [msgQueueLimit=" + msgQueueLimit +
> ", slowClientQueueLimit=" + slowClientQueueLimit + ']');
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10092) Race in partition state when checkpoint started at the middle of starts caches
[ https://issues.apache.org/jira/browse/IGNITE-10092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670529#comment-16670529 ] Dmitriy Pavlov commented on IGNITE-10092: - Hi [~v.pyatkov] could you please fill the ticket description? How a contributor could understand what is to be done here? > Race in partition state when checkpoint started at the middle of starts caches > -- > > Key: IGNITE-10092 > URL: https://issues.apache.org/jira/browse/IGNITE-10092 > Project: Ignite > Issue Type: Bug >Reporter: Vladislav Pyatkov >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9996) Investigate possible performance drop in FSYNC mode for ignite-2.7 compared to ignite-2.6
[ https://issues.apache.org/jira/browse/IGNITE-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670515#comment-16670515 ] ASF GitHub Bot commented on IGNITE-9996: Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/5215 > Investigate possible performance drop in FSYNC mode for ignite-2.7 compared > to ignite-2.6 > - > > Key: IGNITE-9996 > URL: https://issues.apache.org/jira/browse/IGNITE-9996 > Project: Ignite > Issue Type: Task >Reporter: Alexey Goncharuk >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-29 at 3.30.51 PM.png, Screen Shot > 2018-10-31 at 10.30.26 AM.png > > > As per the latest reports we probably have a performance drop around 5-8% on > write benchmarks in FSYNC mode. The cause needs to be investigated and fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10064) Build examples project failed
[
https://issues.apache.org/jira/browse/IGNITE-10064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670514#comment-16670514
]
Dmitriy Pavlov commented on IGNITE-10064:
-
[~skozlov], [~agoncharuk] could you please let me know if PR can be merged?
> Build examples project failed
> -
>
> Key: IGNITE-10064
> URL: https://issues.apache.org/jira/browse/IGNITE-10064
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
>
> 1. Import {{examples/pom.xml}} in IDEA and compile
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project ignite-examples: Compilation failure: Compilation failure:
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[25,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[26,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[27,57]
> package org.apache.ignite.springdata20.repository.support does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[43,2]
> cannot find symbol
> [ERROR] symbol: class EnableIgniteRepositories
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[23,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[24,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[25,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[34,43]
> cannot find symbol
> [ERROR] symbol: class IgniteRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[33,2]
> cannot find symbol
> [ERROR] symbol: class RepositoryConfig
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[56,6]
> cannot find symbol
> [ERROR] symbol: class Query
> [ERROR] location: interface
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[62,13]
> cannot find symbol
> [ERROR] symbol: method deleteAll()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[64,60]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[101,13]
> cannot find symbol
> [ERROR] symbol: method
> save(java.util.TreeMap)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[103,49]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[111,29]
> cannot find symbol
> [ERROR] symbol: method findById(long)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[122,40]
> cannot find symbol
> [ERROR] symbol: method findAllById(java.util.ArrayList)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR] -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-10064) Build examples project failed
[
https://issues.apache.org/jira/browse/IGNITE-10064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-10064:
---
Assignee: Alexey Goncharuk (was: Dmitriy Pavlov)
> Build examples project failed
> -
>
> Key: IGNITE-10064
> URL: https://issues.apache.org/jira/browse/IGNITE-10064
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.7
>
>
> 1. Import {{examples/pom.xml}} in IDEA and compile
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project ignite-examples: Compilation failure: Compilation failure:
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[25,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[26,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[27,57]
> package org.apache.ignite.springdata20.repository.support does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[43,2]
> cannot find symbol
> [ERROR] symbol: class EnableIgniteRepositories
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[23,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[24,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[25,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[34,43]
> cannot find symbol
> [ERROR] symbol: class IgniteRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[33,2]
> cannot find symbol
> [ERROR] symbol: class RepositoryConfig
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[56,6]
> cannot find symbol
> [ERROR] symbol: class Query
> [ERROR] location: interface
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[62,13]
> cannot find symbol
> [ERROR] symbol: method deleteAll()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[64,60]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[101,13]
> cannot find symbol
> [ERROR] symbol: method
> save(java.util.TreeMap)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[103,49]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[111,29]
> cannot find symbol
> [ERROR] symbol: method findById(long)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[122,40]
> cannot find symbol
> [ERROR] symbol: method findAllById(java.util.ArrayList)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR] -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9996) Investigate possible performance drop in FSYNC mode for ignite-2.7 compared to ignite-2.6
[ https://issues.apache.org/jira/browse/IGNITE-9996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670481#comment-16670481 ] Nikolay Izhikov commented on IGNITE-9996: - https://ci.ignite.apache.org/viewQueued.html?itemId=2210636 - Run All > Investigate possible performance drop in FSYNC mode for ignite-2.7 compared > to ignite-2.6 > - > > Key: IGNITE-9996 > URL: https://issues.apache.org/jira/browse/IGNITE-9996 > Project: Ignite > Issue Type: Task >Reporter: Alexey Goncharuk >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > Attachments: Screen Shot 2018-10-29 at 3.30.51 PM.png, Screen Shot > 2018-10-31 at 10.30.26 AM.png > > > As per the latest reports we probably have a performance drop around 5-8% on > write benchmarks in FSYNC mode. The cause needs to be investigated and fixed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10099) `
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruslan Kamashev updated IGNITE-10099: - Summary: ` (was: ClusterNodeAttributeAffinityBackupFilter isn't available in Java config) > ` > - > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Assignee: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruslan Kamashev updated IGNITE-10099: - Summary: ClusterNodeAttributeAffinityBackupFilter isn't available in Java config (was: `) > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Assignee: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670470#comment-16670470 ] Dmitriy Pavlov commented on IGNITE-10099: - [~rynffoll] I've added your account to the list of contributors, so you can assign an issue to yourself. I've also assigned this one to you, I hope you don't mind > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Assignee: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reassigned IGNITE-10099: --- Assignee: Ruslan Kamashev > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Assignee: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670469#comment-16670469 ] Dmitriy Pavlov commented on IGNITE-10099: - [~rynffoll] please set Patch Available state for the issue if you feel fix is ready. Also usually we run all tests and check results, but here I believe we don't need run. > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML
[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670422#comment-16670422 ] Ruslan Kamashev commented on IGNITE-9365: - [~dpavlov] https://issues.apache.org/jira/browse/IGNITE-10099 > Force backups to different AWS availability zones using only Spring XML > --- > > Key: IGNITE-9365 > URL: https://issues.apache.org/jira/browse/IGNITE-9365 > Project: Ignite > Issue Type: Improvement > Components: cache > Environment: >Reporter: David Harvey >Assignee: David Harvey >Priority: Minor > Fix For: 2.7 > > Attachments: master_947962f785_availability_zones_via_spring.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > As a developer, I want to be able to force cache backups each to a different > "Availability Zone", when I'm running out-of-the-box Ignite, without > additional Jars installed. "Availability zone" is a AWS feature with > different names for the same function by other cloud providers. A single > availability zone has the characteristic that some or all of the EC2 > instances in that zone can fail together due to a single fault. You have no > control over the hosts on which the EC2 instance VMs run on in AWS, except by > controlling the availability zone . > > I could write a few lines of a custom affinityBackupFilter, and configure it > a RendezvousAffinityFunction, but then I have to get it deployed on all nodes > in the cluster, and peer class loading will not work to this. The code to > do this should just be part of Ignite. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670419#comment-16670419 ] Ruslan Kamashev edited comment on IGNITE-10099 at 10/31/18 5:28 PM: New Github PR: [https://github.com/apache/ignite/pull/5226] was (Author: rynffoll): Github PR: https://github.com/apache/ignite/pull/5226 > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670419#comment-16670419 ] Ruslan Kamashev commented on IGNITE-10099: -- Github PR: https://github.com/apache/ignite/pull/5226 > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
[ https://issues.apache.org/jira/browse/IGNITE-10099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670417#comment-16670417 ] ASF GitHub Bot commented on IGNITE-10099: - GitHub user rynffoll opened a pull request: https://github.com/apache/ignite/pull/5226 IGNITE-10099 You can merge this pull request into a Git repository by running: $ git pull https://github.com/rynffoll/ignite IGNITE-10099 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5226.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 #5226 commit fdb78a8b6d0331975e61df16af2f109b1bfed9a9 Author: Ruslan Kamashev Date: 2018-10-30T18:25:13Z Make constructor public > ClusterNodeAttributeAffinityBackupFilter isn't available in Java config > --- > > Key: IGNITE-10099 > URL: https://issues.apache.org/jira/browse/IGNITE-10099 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ruslan Kamashev >Priority: Minor > Fix For: 2.8 > > > Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 > ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, > because constructor is package-private. > For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML
[ https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670415#comment-16670415 ] ASF GitHub Bot commented on IGNITE-9365: Github user rynffoll closed the pull request at: https://github.com/apache/ignite/pull/5217 > Force backups to different AWS availability zones using only Spring XML > --- > > Key: IGNITE-9365 > URL: https://issues.apache.org/jira/browse/IGNITE-9365 > Project: Ignite > Issue Type: Improvement > Components: cache > Environment: >Reporter: David Harvey >Assignee: David Harvey >Priority: Minor > Fix For: 2.7 > > Attachments: master_947962f785_availability_zones_via_spring.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > As a developer, I want to be able to force cache backups each to a different > "Availability Zone", when I'm running out-of-the-box Ignite, without > additional Jars installed. "Availability zone" is a AWS feature with > different names for the same function by other cloud providers. A single > availability zone has the characteristic that some or all of the EC2 > instances in that zone can fail together due to a single fault. You have no > control over the hosts on which the EC2 instance VMs run on in AWS, except by > controlling the availability zone . > > I could write a few lines of a custom affinityBackupFilter, and configure it > a RendezvousAffinityFunction, but then I have to get it deployed on all nodes > in the cluster, and peer class loading will not work to this. The code to > do this should just be part of Ignite. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10099) ClusterNodeAttributeAffinityBackupFilter isn't available in Java config
Ruslan Kamashev created IGNITE-10099: Summary: ClusterNodeAttributeAffinityBackupFilter isn't available in Java config Key: IGNITE-10099 URL: https://issues.apache.org/jira/browse/IGNITE-10099 Project: Ignite Issue Type: Bug Components: cache Affects Versions: 2.7 Reporter: Ruslan Kamashev Fix For: 2.8 Original issue: https://issues.apache.org/jira/browse/IGNITE-9365 ClusterNodeAttributeAffinityBackupFilter is available only in Spring config, because constructor is package-private. For support Java config, we should make constructor public. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10091) [TC Bot] Replace PR source for autocompleting branch fields
[
https://issues.apache.org/jira/browse/IGNITE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670392#comment-16670392
]
ASF GitHub Bot commented on IGNITE-10091:
-
asfgit closed pull request #56: IGNITE-10091 Replace PR source for
autocompleting branch fields
URL: https://github.com/apache/ignite-teamcity-bot/pull/56
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/github/ignited/GitHubConnIgnitedImpl.java
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/github/ignited/GitHubConnIgnitedImpl.java
index 3b998ee3..6a373668 100644
---
a/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/github/ignited/GitHubConnIgnitedImpl.java
+++
b/ignite-tc-helper-web/src/main/java/org/apache/ignite/ci/github/ignited/GitHubConnIgnitedImpl.java
@@ -52,6 +52,7 @@
/** Ignite provider. */
@Inject Provider igniteProvider;
+
/** Scheduler. */
@Inject IScheduler scheduler;
@@ -93,7 +94,7 @@ public void init(String srvId, IGitHubConnection conn) {
}
private void actualizePrs() {
-runAtualizePrs(srvId, false);
+runActualizePrs(srvId, false);
// schedule full resync later
scheduler.invokeLater(this::sheduleResync, 20, TimeUnit.SECONDS);
@@ -111,7 +112,7 @@ private void sheduleResync() {
*
*/
private void fullReindex() {
-runAtualizePrs(srvId, true);
+runActualizePrs(srvId, true);
}
/**
@@ -120,7 +121,7 @@ private void fullReindex() {
*/
@MonitoredTask(name = "Actualize PRs(srv, full resync)",
nameExtArgsIndexes = {0, 1})
@AutoProfiling
-protected String runAtualizePrs(String srvId, boolean fullReindex) {
+protected String runActualizePrs(String srvId, boolean fullReindex) {
AtomicReference outLinkNext = new AtomicReference<>();
List ghData = conn.getPullRequests(null, outLinkNext);
diff --git a/ignite-tc-helper-web/src/main/webapp/index0.html
b/ignite-tc-helper-web/src/main/webapp/index0.html
index 01106132..33ebb0fa 100644
--- a/ignite-tc-helper-web/src/main/webapp/index0.html
+++ b/ignite-tc-helper-web/src/main/webapp/index0.html
@@ -51,9 +51,8 @@
$.ajax({
url: "rest/branches/getServerIds",
success: function(result) {
-$("#loadStatus").html("");
-setupAutocompleteList(result);
showBuildsOnServers(result);
+setAutocompleteFilter();
},
error: showErrInLoadStatus
});
@@ -102,17 +101,28 @@
function showBuildsOnServers(result) {
var res = "";
+
for (var i = 0; i < result.length; i++) {
-var serverId = result[i];
+let srvId = result[i];
//res+="Check
PR";
res+="";
-res+="Server: " ;
+res+="Server: " ;
res+="Check Logs: " ;
res+="Build Id: ";
res+="";
res+="";
+
+$.ajax({
+url: "rest/visa/contributions?serverId=" + srvId,
+success:
+function (result) {
+$("#loadStatus").html("");
+fillBranchAutocompleteList(result, srvId);
+}
+});
}
+
$("#buildsCheck").html(res);
}
diff --git a/ignite-tc-helper-web/src/main/webapp/js/common-1.6.js
b/ignite-tc-helper-web/src/main/webapp/js/common-1.6.js
index 613e4114..22469d5d 100644
--- a/ignite-tc-helper-web/src/main/webapp/js/common-1.6.js
+++ b/ignite-tc-helper-web/src/main/webapp/js/common-1.6.js
@@ -272,93 +272,27 @@ var gitUrls = new Map();
var branchesForTc = {};
/**
- * Fill git URLs and send requests to them.
+ * Fill autocomplete lists for the fields branchForTc.
*
- * @param srvIds - Set of server IDs.
+ * @param result List of ContributionToCheck.
+ * @param srvId Server id.
*/
-function setupAutocompleteList(srvIds) {
-for (let srvId of srvIds)
-gitUrls.set(srvId, "");
-
-setAutocompleteFilter();
-
-startFillAutocompleteListsProcess();
-}
-
-/**
- * Retrieves recent PR numbers and fills autocomplete lists for the fields
branchForTc.
- */
-function startFillAutocompleteListsProcess() {
-_receiveIntegrationUrls();
-}
-
-/**
- * Receive api links for the servers.
- *
- * @private
- */
-function _receiveIntegrationUrls() {
-var url = "rest/build/integrationUrls?serverIds=";
-
-for (let key of gitUrls.keys())
-url += key + ",";
-
-$.ajax({
-url: url,
-success: function (result) {
-_fillGitUrls(result);
-_sendRequestsToFillAutocompleteLists();
-}
-});
-}
-
-/**
- * Fill git api URLs.
- *
- * @param result Array of
[jira] [Commented] (IGNITE-10045) Add fail-fast mode to bounded iteration of StandaloneWalRecordsIterator
[ https://issues.apache.org/jira/browse/IGNITE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670382#comment-16670382 ] Dmitriy Pavlov commented on IGNITE-10045: - I find this change is looking good except 1 usability concern I have related to usability. I left comment in the PR. > Add fail-fast mode to bounded iteration of StandaloneWalRecordsIterator > --- > > Key: IGNITE-10045 > URL: https://issues.apache.org/jira/browse/IGNITE-10045 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Rakov >Assignee: Alexey Stelmak >Priority: Major > Fix For: 2.8 > > > Since IGNITE-9294 StandaloneWalRecordsIterator supports bounded iteration. > That means we can specify "from" and "to" WAL pointers and iterator will > return records only between given bounds. > The problem is that in current implementation StandaloneWalRecordsIterator > just skips segments if they are missing. For example: if we'll specify > fromIdx=0, toIdx = 10 and segments with indexes=[9, 10] will be missing, > we'll just silently finish iteration on idx=8. > To prevent that, we should be able to switch on fail-fast mode, in which > StandaloneWalRecordsIterator will throw error unless iteration is really > started from left bound and ended on right bound. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10098) TcpCommunicationSpi for .NET misses some properties of java TcpCommunicationSpi
Maxim Pudov created IGNITE-10098: Summary: TcpCommunicationSpi for .NET misses some properties of java TcpCommunicationSpi Key: IGNITE-10098 URL: https://issues.apache.org/jira/browse/IGNITE-10098 Project: Ignite Issue Type: Task Components: platforms Affects Versions: 1.6 Reporter: Maxim Pudov Fix For: 2.8 For example, socketWriteTimeout. It might be helpful to create an API parity test for this class. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9893) add hibernate-5.2 module
[ https://issues.apache.org/jira/browse/IGNITE-9893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670363#comment-16670363 ] Scott Feldstein commented on IGNITE-9893: - hi [~ilyak], I used hibernate 5.2 because that's the version that spring boot 2.0.x is using. That being said, spring boot 2.1.x just came out within the last few days and it uses hibernate 5.3.. I would suggest that we commit 5.2 and work off of that to get the hibernate 5.3 spi working. I'm not sure when I'll get to it, but knowing our developers they'll want to use spring boot 2.1.x right away so I'll probably start hacking away at it in the next couple weeks. So question to you - what do you want to do? I just rebased the latest ignite master locally and I'm recompiling and retesting to ensure that everything is good to go. Once that happens I'll update the pull request. > add hibernate-5.2 module > > > Key: IGNITE-9893 > URL: https://issues.apache.org/jira/browse/IGNITE-9893 > Project: Ignite > Issue Type: New Feature > Components: hibernate >Reporter: Scott Feldstein >Assignee: Scott Feldstein >Priority: Major > > hi, > I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD. > commit: > [https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9] > All tests pass except > CacheHibernateBlobStoreSelfTest.testSimpleMultithreading which is carryover > from the hibernate-5.1 implementation. There is a bug already associated with > the failure: > https://issues.apache.org/jira/browse/IGNITE-1757 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-6389) Cache.invoke fails on atomic cache with configured AccessedExpiryPolicy
[
https://issues.apache.org/jira/browse/IGNITE-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Mekhanikov resolved IGNITE-6389.
--
Resolution: Cannot Reproduce
> Cache.invoke fails on atomic cache with configured AccessedExpiryPolicy
> ---
>
> Key: IGNITE-6389
> URL: https://issues.apache.org/jira/browse/IGNITE-6389
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Mekhanikov
>Priority: Major
>
> When calling {{invoke(...)}} on atomic cache with {{AccessedExpiryPolicy}},
> and the target key already exists in cache, then the following exception is
> thrown:
> {noformat}
> [2017-09-15 12:10:18,435][ERROR][main][GridDhtAtomicCache] Unexpected
> exception during cache update
> class org.apache.ignite.IgniteException: Runtime failure on search row:
> org.apache.ignite.internal.processors.cache.tree.SearchRow@7334aada
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1632)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:1201)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:343)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1693)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateSingle(GridDhtAtomicCache.java:2481)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update(GridDhtAtomicCache.java:1944)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal0(GridDhtAtomicCache.java:1797)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.updateAllAsyncInternal(GridDhtAtomicCache.java:1689)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.sendSingleRequest(GridNearAtomicAbstractUpdateFuture.java:299)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.map(GridNearAtomicSingleUpdateFuture.java:483)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:443)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1170)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke0(GridDhtAtomicCache.java:879)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.invoke(GridDhtAtomicCache.java:837)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1338)
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.invoke(IgniteCacheProxyImpl.java:1384)
> at
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.invoke(GatewayProtectedCacheProxy.java:1348)
> at org.apache.ignite.examples.ExpiryExample.main(ExpiryExample.java:67)
> Caused by: java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.createRow(IgniteCacheOffheapManagerImpl.java:1253)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.initResultOnCancelUpdate(GridCacheMapEntry.java:4270)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:4157)
> at
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry$AtomicCacheUpdateClosure.call(GridCacheMapEntry.java:3921)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.invokeClosure(BPlusTree.java:2988)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Invoke.access$6200(BPlusTree.java:2882)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invokeDown(BPlusTree.java:1719)
> at
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.invoke(BPlusTree.java:1602)
> ... 18 more
> Exception in thread "main"
> org.apache.ignite.cache.CachePartialUpdateException: Failed to update keys
> (retry update if possible).: [1]
> at
>
[jira] [Assigned] (IGNITE-7611) Document logger configuration options
[ https://issues.apache.org/jira/browse/IGNITE-7611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-7611: --- Assignee: Stanislav Lukyanov (was: Prachi Garg) > Document logger configuration options > - > > Key: IGNITE-7611 > URL: https://issues.apache.org/jira/browse/IGNITE-7611 > Project: Ignite > Issue Type: Bug > Components: documentation >Reporter: Stanislav Lukyanov >Assignee: Stanislav Lukyanov >Priority: Major > Fix For: 2.7 > > > Existing documentation on readme.io > (https://apacheignite.readme.io/docs/logging) gives details on how to enable > each of the supported logging frameworks, and some info on the default > configuration (e.g. IGNITE_QUIET). > The documentation should also cover some other features of Ignite logging, > such as recently added features of automatic reconfiguration of log4j 1.x and > 2.x (IGNITE-6946) and DEV_ONLY marker in logging messages (IGNITE-7284), as > well as other features like automatic metrics logging (MetricsLogFrequency) > and performance suggestions on start > (IGNITE_PERFORMANCE_SUGGESTIONS_DISABLED). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9817) Update documentation and examples for Spark SQL Table Specification
[ https://issues.apache.org/jira/browse/IGNITE-9817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-9817: --- Assignee: Nikolay Izhikov (was: Prachi Garg) > Update documentation and examples for Spark SQL Table Specification > --- > > Key: IGNITE-9817 > URL: https://issues.apache.org/jira/browse/IGNITE-9817 > Project: Ignite > Issue Type: Sub-task > Components: documentation >Reporter: Nikolay Izhikov >Assignee: Nikolay Izhikov >Priority: Major > Fix For: 2.7 > > > We should update documentation and examples according to the results of > IGNITE-9228. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10012) Add Transactional SQL feature description to Ignite website
[ https://issues.apache.org/jira/browse/IGNITE-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg updated IGNITE-10012: - Component/s: site > Add Transactional SQL feature description to Ignite website > --- > > Key: IGNITE-10012 > URL: https://issues.apache.org/jira/browse/IGNITE-10012 > Project: Ignite > Issue Type: Task > Components: documentation, site >Reporter: Prachi Garg >Assignee: Prachi Garg >Priority: Major > Fix For: 2.7 > > > [~Artem Budnikov], Please provide some information/ link to the documentation > about this feature so that some description can be added to the website. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-9619) Document REST "getall" array format
[ https://issues.apache.org/jira/browse/IGNITE-9619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prachi Garg reassigned IGNITE-9619: --- Assignee: Ilya Kasnacheev (was: Prachi Garg) > Document REST "getall" array format > --- > > Key: IGNITE-9619 > URL: https://issues.apache.org/jira/browse/IGNITE-9619 > Project: Ignite > Issue Type: Improvement > Components: documentation >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Minor > Labels: documentation > Fix For: 2.7 > > > https://apacheignite.readme.io/docs/rest-api#get-all <-- this page should > have a section about new IGNITE_REST_GETALL_AS_ARRAY System Property, as well > as an example of response after it is set. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10045) Add fail-fast mode to bounded iteration of StandaloneWalRecordsIterator
[
https://issues.apache.org/jira/browse/IGNITE-10045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670317#comment-16670317
]
Ignite TC Bot commented on IGNITE-10045:
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2194724buildTypeId=IgniteTests24Java8_RunAll]
> Add fail-fast mode to bounded iteration of StandaloneWalRecordsIterator
> ---
>
> Key: IGNITE-10045
> URL: https://issues.apache.org/jira/browse/IGNITE-10045
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.8
>
>
> Since IGNITE-9294 StandaloneWalRecordsIterator supports bounded iteration.
> That means we can specify "from" and "to" WAL pointers and iterator will
> return records only between given bounds.
> The problem is that in current implementation StandaloneWalRecordsIterator
> just skips segments if they are missing. For example: if we'll specify
> fromIdx=0, toIdx = 10 and segments with indexes=[9, 10] will be missing,
> we'll just silently finish iteration on idx=8.
> To prevent that, we should be able to switch on fail-fast mode, in which
> StandaloneWalRecordsIterator will throw error unless iteration is really
> started from left bound and ended on right bound.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10097) Document how to disable self-registration on Web Console
Alexey Kuznetsov created IGNITE-10097: - Summary: Document how to disable self-registration on Web Console Key: IGNITE-10097 URL: https://issues.apache.org/jira/browse/IGNITE-10097 Project: Ignite Issue Type: Task Components: documentation Reporter: Alexey Kuznetsov Assignee: Artem Budnikov See IGNITE-9941 for details -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10096) Document new "caches" param for "top" command in REST API.
Alexey Kuznetsov created IGNITE-10096: - Summary: Document new "caches" param for "top" command in REST API. Key: IGNITE-10096 URL: https://issues.apache.org/jira/browse/IGNITE-10096 Project: Ignite Issue Type: Task Components: documentation Reporter: Alexey Kuznetsov Assignee: Artem Budnikov See IGNITE-10031 for more info -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10095) [TC Bot] Support Build Parameters storage in bot's DB and in run statistics
Dmitriy Pavlov created IGNITE-10095: --- Summary: [TC Bot] Support Build Parameters storage in bot's DB and in run statistics Key: IGNITE-10095 URL: https://issues.apache.org/jira/browse/IGNITE-10095 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov [TC Bot] Support Build Parameters storage in bot's DB, and support propagation of these parameters into run statistics It is needed to have a future opportunity to separate Java 8,10,11 Runs and also runs with short test set and full overnight run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10094) TC: Introduce overnight builds
[ https://issues.apache.org/jira/browse/IGNITE-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670281#comment-16670281 ] Dmitriy Pavlov commented on IGNITE-10094: - I suggest using only not environment variable but some build parameter, similar with java home, so TC bot can see this parameter from TC REST API: > TC: Introduce overnight builds > -- > > Key: IGNITE-10094 > URL: https://issues.apache.org/jira/browse/IGNITE-10094 > Project: Ignite > Issue Type: Task >Reporter: Alexey Goncharuk >Priority: Major > > Creating this ticket to collect all efforts on shortening a single TC run and > introduce overnight TC runs. > From the infrastructure side, we need to create a separate run configuration > (for example, Run All Nightly). To begin, Run All Nightly will delegate to > Run All and later we will move several long-running suites to the nightly > run. Nightly Run All should have a nightly trigger. > From the TC bot side, we need to configure it to push nightly builds when TC > is idle and additionally to track new failures in nightly runs. > From the code side, we need to define an environment property that should > distinguish a quick run from the nightly run. Later this property will be > used to scale tests duration. > [~dpavlov], [~sergey-chugunov], [~vveider], can you chime in? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9442) Collocated IgniteSet#close is not working on non-affinity node.
[
https://issues.apache.org/jira/browse/IGNITE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670279#comment-16670279
]
Pavel Pereslegin commented on IGNITE-9442:
--
[~Mmuzaf], can you review this small fix?
> Collocated IgniteSet#close is not working on non-affinity node.
> ---
>
> Key: IGNITE-9442
> URL: https://issues.apache.org/jira/browse/IGNITE-9442
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Attachments: Reproducer.java
>
>
> Method {{close()}} in collocated {{IgniteSet}} works incorrectly if cluster
> contains non-affinity nodes.
> Steps to reproduce:
> 1. Start cluster with two nodes: server and client.
> 2. Create collocated {{IgniteSet}} on client node.
> 3. Close {{IgniteSet}} on client node.
> 4. Invoke {{add()}} method on closed IgniteSet.
> Expected: {{add()}} throws {{IllegalStateException}}.
> Actual: {{add()}} does not throw exception and put new "orphan" item in the
> datastructure cache.
> Alternatively to client node we can exclude server node by using cache node
> filter, as shown in attached junit reproducer.
> This bug is related to
> [IGNITE-6346|https://issues.apache.org/jira/browse/IGNITE-6346], which also
> affects usage of IgniteSet in cluster with non-affinity nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9442) Collocated IgniteSet#close is not working on non-affinity node.
[
https://issues.apache.org/jira/browse/IGNITE-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670268#comment-16670268
]
Ignite TC Bot commented on IGNITE-9442:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2184010buildTypeId=IgniteTests24Java8_RunAll]
> Collocated IgniteSet#close is not working on non-affinity node.
> ---
>
> Key: IGNITE-9442
> URL: https://issues.apache.org/jira/browse/IGNITE-9442
> Project: Ignite
> Issue Type: Bug
> Components: data structures
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
> Attachments: Reproducer.java
>
>
> Method {{close()}} in collocated {{IgniteSet}} works incorrectly if cluster
> contains non-affinity nodes.
> Steps to reproduce:
> 1. Start cluster with two nodes: server and client.
> 2. Create collocated {{IgniteSet}} on client node.
> 3. Close {{IgniteSet}} on client node.
> 4. Invoke {{add()}} method on closed IgniteSet.
> Expected: {{add()}} throws {{IllegalStateException}}.
> Actual: {{add()}} does not throw exception and put new "orphan" item in the
> datastructure cache.
> Alternatively to client node we can exclude server node by using cache node
> filter, as shown in attached junit reproducer.
> This bug is related to
> [IGNITE-6346|https://issues.apache.org/jira/browse/IGNITE-6346], which also
> affects usage of IgniteSet in cluster with non-affinity nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10094) TC: Introduce overnight builds
[ https://issues.apache.org/jira/browse/IGNITE-10094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670265#comment-16670265 ] Dmitriy Pavlov commented on IGNITE-10094: - For configuring a new build to trigger I need just an ID of new config. > TC: Introduce overnight builds > -- > > Key: IGNITE-10094 > URL: https://issues.apache.org/jira/browse/IGNITE-10094 > Project: Ignite > Issue Type: Task >Reporter: Alexey Goncharuk >Priority: Major > > Creating this ticket to collect all efforts on shortening a single TC run and > introduce overnight TC runs. > From the infrastructure side, we need to create a separate run configuration > (for example, Run All Nightly). To begin, Run All Nightly will delegate to > Run All and later we will move several long-running suites to the nightly > run. Nightly Run All should have a nightly trigger. > From the TC bot side, we need to configure it to push nightly builds when TC > is idle and additionally to track new failures in nightly runs. > From the code side, we need to define an environment property that should > distinguish a quick run from the nightly run. Later this property will be > used to scale tests duration. > [~dpavlov], [~sergey-chugunov], [~vveider], can you chime in? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10094) TC: Introduce overnight builds
Alexey Goncharuk created IGNITE-10094: - Summary: TC: Introduce overnight builds Key: IGNITE-10094 URL: https://issues.apache.org/jira/browse/IGNITE-10094 Project: Ignite Issue Type: Task Reporter: Alexey Goncharuk Creating this ticket to collect all efforts on shortening a single TC run and introduce overnight TC runs. >From the infrastructure side, we need to create a separate run configuration >(for example, Run All Nightly). To begin, Run All Nightly will delegate to Run >All and later we will move several long-running suites to the nightly run. >Nightly Run All should have a nightly trigger. >From the TC bot side, we need to configure it to push nightly builds when TC >is idle and additionally to track new failures in nightly runs. >From the code side, we need to define an environment property that should >distinguish a quick run from the nightly run. Later this property will be used >to scale tests duration. [~dpavlov], [~sergey-chugunov], [~vveider], can you chime in? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (IGNITE-9850) Python thin: Find out the cause of the python's client low performance
[ https://issues.apache.org/jira/browse/IGNITE-9850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego resolved IGNITE-9850. - Resolution: Fixed [~Melnichuk], sounds reasonable to me. Closing the issue. > Python thin: Find out the cause of the python's client low performance > -- > > Key: IGNITE-9850 > URL: https://issues.apache.org/jira/browse/IGNITE-9850 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > According to benchmarks results reported by IGNITE-9824, python thin client > is 3 to 4 times slower than Java client. We need to find out the root cause > of this and if we can fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10093) Consider adding documentation page with performance analysis of thin clients
Igor Sapego created IGNITE-10093: Summary: Consider adding documentation page with performance analysis of thin clients Key: IGNITE-10093 URL: https://issues.apache.org/jira/browse/IGNITE-10093 Project: Ignite Issue Type: Task Components: documentation, thin client Reporter: Igor Sapego Maybe this is a good idea to add a page on readme.io where we will describe (without numbers) performance features of different thin clients. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10002) MVCC: Create "Cache 2" test suite for MVCC mode.
[ https://issues.apache.org/jira/browse/IGNITE-10002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670249#comment-16670249 ] Andrew Mashenkov commented on IGNITE-10002: --- TC looks good. > MVCC: Create "Cache 2" test suite for MVCC mode. > > > Key: IGNITE-10002 > URL: https://issues.apache.org/jira/browse/IGNITE-10002 > Project: Ignite > Issue Type: Sub-task > Components: mvcc >Reporter: Andrew Mashenkov >Assignee: Andrew Mashenkov >Priority: Major > > Create MVCC version of IgniteCacheTestSuite2 and add it to TC. > All non-relevant tests should be marked as ignored. > Failed tests should be muted and tickets should be created for unknown > failure reasons. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-8896) Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()
[
https://issues.apache.org/jira/browse/IGNITE-8896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670248#comment-16670248
]
ASF GitHub Bot commented on IGNITE-8896:
GitHub user Rodion4ik opened a pull request:
https://github.com/apache/ignite/pull/5225
IGNITE-8896
In TcpCommunicationSpi text of message "greater than" replace on "greater
than or equal to" according to conditions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Rodion4ik/ignite ignite-8896
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5225.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 #5225
commit 8a312d6087c0608352c49a08cdd31c1f8a65a54e
Author: Rodion4ik
Date: 2018-10-31T14:21:47Z
Update TcpCommunicationSpi.java
> Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()
> ---
>
> Key: IGNITE-8896
> URL: https://issues.apache.org/jira/browse/IGNITE-8896
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Karachentsev
>Assignee: Rodion
>Priority: Minor
> Labels: newbie
> Fix For: 2.8
>
>
> Javadoc for TcpCommunicationSpi.setSlowClientQueueLimit() says that is should
> be set to value equal to TcpCommunicationSpi.getMessageQueueLimit().
> But this is wrong, because first checks back pressure limit and sender thread
> will be blocked before slow client check. Also, warning checks the value
> correctly, but message should be "...greater or equal...":
> {code:java}
> if (slowClientQueueLimit > 0 && msgQueueLimit > 0 && slowClientQueueLimit >=
> msgQueueLimit) {
> U.quietAndWarn(log, "Slow client queue limit is set to a value
> greater than message queue limit " +
> "(slow client queue limit will have no effect)
> [msgQueueLimit=" + msgQueueLimit +
> ", slowClientQueueLimit=" + slowClientQueueLimit + ']');
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10064) Build examples project failed
[
https://issues.apache.org/jira/browse/IGNITE-10064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670245#comment-16670245
]
ASF GitHub Bot commented on IGNITE-10064:
-
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/5224
IGNITE-10064 Fixed examples pom files
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10064
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5224.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 #5224
commit d83094e1d614034ee59aa33ae8edaaa611889092
Author: Alexey Goncharuk
Date: 2018-10-31T15:29:08Z
IGNITE-10064 Fixed examples pom files
> Build examples project failed
> -
>
> Key: IGNITE-10064
> URL: https://issues.apache.org/jira/browse/IGNITE-10064
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.7
>
>
> 1. Import {{examples/pom.xml}} in IDEA and compile
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project ignite-examples: Compilation failure: Compilation failure:
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[25,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[26,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[27,57]
> package org.apache.ignite.springdata20.repository.support does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[43,2]
> cannot find symbol
> [ERROR] symbol: class EnableIgniteRepositories
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[23,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[24,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[25,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[34,43]
> cannot find symbol
> [ERROR] symbol: class IgniteRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[33,2]
> cannot find symbol
> [ERROR] symbol: class RepositoryConfig
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[56,6]
> cannot find symbol
> [ERROR] symbol: class Query
> [ERROR] location: interface
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[62,13]
> cannot find symbol
> [ERROR] symbol: method deleteAll()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[64,60]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[101,13]
> cannot find symbol
> [ERROR] symbol: method
> save(java.util.TreeMap)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[103,49]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[111,29]
> cannot find symbol
> [ERROR] symbol: method findById(long)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
>
[jira] [Commented] (IGNITE-10064) Build examples project failed
[
https://issues.apache.org/jira/browse/IGNITE-10064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670241#comment-16670241
]
Alexey Goncharuk commented on IGNITE-10064:
---
[~dpavlov] the original ticket did not update {{examples/pom-standalone.xml}}
and {{examples/pom-standalone-lgpl.xml}}. We need to replace
{{ignite-spring-data}} with {{ignite-spring-data_2.0}} in these files.
> Build examples project failed
> -
>
> Key: IGNITE-10064
> URL: https://issues.apache.org/jira/browse/IGNITE-10064
> Project: Ignite
> Issue Type: Bug
> Components: examples
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Dmitriy Pavlov
>Priority: Critical
> Fix For: 2.7
>
>
> 1. Import {{examples/pom.xml}} in IDEA and compile
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project ignite-examples: Compilation failure: Compilation failure:
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[25,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[26,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[27,57]
> package org.apache.ignite.springdata20.repository.support does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringAppCfg.java:[43,2]
> cannot find symbol
> [ERROR] symbol: class EnableIgniteRepositories
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[23,49]
> package org.apache.ignite.springdata20.repository does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[24,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[25,56]
> package org.apache.ignite.springdata20.repository.config does not exist
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[34,43]
> cannot find symbol
> [ERROR] symbol: class IgniteRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[33,2]
> cannot find symbol
> [ERROR] symbol: class RepositoryConfig
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/PersonRepository.java:[56,6]
> cannot find symbol
> [ERROR] symbol: class Query
> [ERROR] location: interface
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[62,13]
> cannot find symbol
> [ERROR] symbol: method deleteAll()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[64,60]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[101,13]
> cannot find symbol
> [ERROR] symbol: method
> save(java.util.TreeMap)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[103,49]
> cannot find symbol
> [ERROR] symbol: method count()
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[111,29]
> cannot find symbol
> [ERROR] symbol: method findById(long)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR]
> /C:/Work/2.7/examples/src/main/java/org/apache/ignite/examples/springdata/SpringDataExample.java:[122,40]
> cannot find symbol
> [ERROR] symbol: method findAllById(java.util.ArrayList)
> [ERROR] location: variable repo of type
> org.apache.ignite.examples.springdata.PersonRepository
> [ERROR] -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10092) Race in partition state when checkpoint started at the middle of starts caches
Vladislav Pyatkov created IGNITE-10092: -- Summary: Race in partition state when checkpoint started at the middle of starts caches Key: IGNITE-10092 URL: https://issues.apache.org/jira/browse/IGNITE-10092 Project: Ignite Issue Type: Bug Reporter: Vladislav Pyatkov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10088) Partition is restored in moving state instead of owning if node restarted before first checkpoint.
[
https://issues.apache.org/jira/browse/IGNITE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10088:
---
Description:
This is due to
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore#exists
returning false when called from restorePartitionStates if not enough data was
written to store due to checkpoint.
Reproducer:
{noformat}
package org.apache.ignite.internal.processors.cache.transactions;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
import java.util.Set;
import org.apache.ignite.IgniteDataStreamer;
import org.apache.ignite.IgniteSystemProperties;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
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.failure.StopNodeFailureHandler;
import org.apache.ignite.failure.StopNodeOrHaltFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import org.apache.ignite.internal.managers.communication.GridIoMessage;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxFinishRequest;
import
org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest;
import org.apache.ignite.internal.processors.cache.verify.IdleVerifyResultV2;
import org.apache.ignite.internal.util.typedef.T2;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.lang.IgnitePredicate;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
import static org.apache.ignite.configuration.WALMode.LOG_ONLY;
import static org.apache.ignite.testframework.GridTestUtils.runAsync;
import static org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
import static
org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
/**
* Test data loss on recovery due to missed partition counter on tx messages
reorder.
*/
public class MovingPartitionAfterRestartNoBLTChangeTest extends
GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** */
private static final int GRID_CNT = 2;
/** */
private static final int MB = 1024 * 1024;
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setConsistentId("node" + igniteInstanceName);
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
cfg.setDataStorageConfiguration(new DataStorageConfiguration().
setWalSegmentSize(12 *
MB).setWalMode(LOG_ONLY).setPageSize(1024).setCheckpointFrequency(100L).
setDefaultDataRegionConfiguration(new
DataRegionConfiguration().setPersistenceEnabled(true).
setInitialSize(100 * MB).setMaxSize(100 * MB)));
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(2);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
ccfg.setAffinity(new RendezvousAffinityFunction(false, 1));
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();
cleanPersistenceDir();
}
/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
super.afterTest();
stopAllGrids();
cleanPersistenceDir();
}
public void testMoving() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
[jira] [Updated] (IGNITE-10088) Partition is restored in moving state instead of owning if node restarted before first checkpoint.
[
https://issues.apache.org/jira/browse/IGNITE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10088:
---
Description:
This is due to
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore#exists
returning false if not enough data was writen to store due to checkpoint.
Reproducer:
{noformat}
package org.apache.ignite.internal.processors.cache.transactions;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
import java.util.Set;
import org.apache.ignite.IgniteDataStreamer;
import org.apache.ignite.IgniteSystemProperties;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
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.failure.StopNodeFailureHandler;
import org.apache.ignite.failure.StopNodeOrHaltFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import org.apache.ignite.internal.managers.communication.GridIoMessage;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxFinishRequest;
import
org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest;
import org.apache.ignite.internal.processors.cache.verify.IdleVerifyResultV2;
import org.apache.ignite.internal.util.typedef.T2;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.lang.IgnitePredicate;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
import static org.apache.ignite.configuration.WALMode.LOG_ONLY;
import static org.apache.ignite.testframework.GridTestUtils.runAsync;
import static org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
import static
org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
/**
* Test data loss on recovery due to missed partition counter on tx messages
reorder.
*/
public class MovingPartitionAfterRestartNoBLTChangeTest extends
GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** */
private static final int GRID_CNT = 2;
/** */
private static final int MB = 1024 * 1024;
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setConsistentId("node" + igniteInstanceName);
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
cfg.setDataStorageConfiguration(new DataStorageConfiguration().
setWalSegmentSize(12 *
MB).setWalMode(LOG_ONLY).setPageSize(1024).setCheckpointFrequency(100L).
setDefaultDataRegionConfiguration(new
DataRegionConfiguration().setPersistenceEnabled(true).
setInitialSize(100 * MB).setMaxSize(100 * MB)));
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(2);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
ccfg.setAffinity(new RendezvousAffinityFunction(false, 1));
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();
cleanPersistenceDir();
}
/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
super.afterTest();
stopAllGrids();
cleanPersistenceDir();
}
public void testMoving() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
awaitPartitionMapExchange();
stopGrid(1);
[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[ https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670226#comment-16670226 ] Amelchev Nikita commented on IGNITE-4111: - I have used the new method of test listening method and merged new master one more time. TC tests are OK. > Communication fails to send message if target node did not finish join process > -- > > Key: IGNITE-4111 > URL: https://issues.apache.org/jira/browse/IGNITE-4111 > Project: Ignite > Issue Type: Bug > Components: general >Reporter: Semen Boikov >Assignee: Amelchev Nikita >Priority: Minor > Fix For: 2.8 > > Attachments: test onFirstMessage hang.log > > > Currently this scenario is possible: > - joining node sent join request and waits for > TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology > - others nodes already see this node and can send messages to it (for example > try to run compute job on this node) > - joining node can not receive message: TcpCommunicationSpi will hang inside > 'onFirstMessage' on 'getSpiContext' call, so sending node will get error > trying to establish connection > Possible fix: if in onFirstMessage() spi context is not available, then > TcpCommunicationSpi should send special response which indicates that this > node is not ready yet, and sender should retry after some time. > Also need check internal code for places where message can be unnecessarily > sent to node: one such place is > GridCachePartitionExchangeManager.refreshPartitions - message is sent to all > known nodes, but here we can filter by node order / finished exchage version. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-9850) Python thin: Find out the cause of the python's client low performance
[ https://issues.apache.org/jira/browse/IGNITE-9850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Sapego updated IGNITE-9850: Priority: Major (was: Critical) > Python thin: Find out the cause of the python's client low performance > -- > > Key: IGNITE-9850 > URL: https://issues.apache.org/jira/browse/IGNITE-9850 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Dmitry Melnichuk >Priority: Major > Labels: python > Fix For: 2.8 > > > According to benchmarks results reported by IGNITE-9824, python thin client > is 3 to 4 times slower than Java client. We need to find out the root cause > of this and if we can fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670199#comment-16670199
]
PetrovMikhail edited comment on IGNITE-9149 at 10/31/18 3:09 PM:
-
All failed tests passed locally.
was (Author: petrovmikhail):
All failed tests passe locally.
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10091) [TC Bot] Replace PR source for autocompleting branch fields
[ https://issues.apache.org/jira/browse/IGNITE-10091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670224#comment-16670224 ] ASF GitHub Bot commented on IGNITE-10091: - SomeFire opened a new pull request #56: IGNITE-10091 Replace PR source for autocompleting branch fields URL: https://github.com/apache/ignite-teamcity-bot/pull/56 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [TC Bot] Replace PR source for autocompleting branch fields > --- > > Key: IGNITE-10091 > URL: https://issues.apache.org/jira/browse/IGNITE-10091 > Project: Ignite > Issue Type: Task >Reporter: Ryabov Dmitrii >Assignee: Ryabov Dmitrii >Priority: Minor > > Currently, client receive PRs info for autocompletion list separately from > the server. Instead, we should get this info from the Bot, because it is > cached here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-7153) Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for values > 8kb
[
https://issues.apache.org/jira/browse/IGNITE-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670221#comment-16670221
]
Dmitriy Pavlov commented on IGNITE-7153:
[~roman_s] could you please move the issue to unassigned or assign it to
[~mcfongtw]? it seems there is a fix.
> Redis: BufferUnderflowException at GridRedisProtocolParser.readBulkStr for
> values > 8kb
> ---
>
> Key: IGNITE-7153
> URL: https://issues.apache.org/jira/browse/IGNITE-7153
> Project: Ignite
> Issue Type: Bug
> Components: general
>Affects Versions: 2.3
> Environment: Win, PHP 7, php_redis-3.1.1-7.0
>Reporter: Alexey Popov
>Assignee: Roman Shtykh
>Priority: Major
> Labels: redis
>
> Exception:
> {noformat}
> [15:03:23,690][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Failed to process selector key [ses=GridSelectorNioSessionImpl
> [worker=ByteBufferNioClientWorker [readBuf=java.nio.HeapByteBuffer[pos=28
> lim=8192 cap=8192], super=AbstractNioClientWorker [idx=0, bytesRcvd=0,
> bytesSent=0, bytesRcvd0=0, bytesSent0=0, select=true, super=GridWorker
> [name=grid-nio-worker-tcp-rest-0, igniteInstanceName=null, finished=false,
> hashCode=396395638, interrupted=false,
> runner=grid-nio-worker-tcp-rest-0-#36]]], writeBuf=null, readBuf=null,
> inRecovery=null, outRecovery=null, super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6380, rmtAddr=/127.0.0.1:51794, createTime=1512734602674,
> closeTime=0, bytesSent=0, bytesRcvd=8192, bytesSent0=0, bytesRcvd0=8192,
> sndSchedTime=1512734602674, lastSndTime=1512734602674,
> lastRcvTime=1512734602674, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter [parser=GridTcpRestParser
> [jdkMarshaller=JdkMarshaller [], routerClient=false], directMode=false]],
> accepted=true]]]
> java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:150)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.GridTcpRestParser.decode(GridTcpRestParser.java:70)
> at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3392)
> at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1096)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> [15:03:23,691][SEVERE][grid-nio-worker-tcp-rest-0-#36][GridTcpRestProtocol]
> Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2296)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1717)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.nio.BufferUnderflowException
> at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readBulkStr(GridRedisProtocolParser.java:107)
> at
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.GridRedisProtocolParser.readArray(GridRedisProtocolParser.java:86)
> at
>
[jira] [Commented] (IGNITE-4111) Communication fails to send message if target node did not finish join process
[
https://issues.apache.org/jira/browse/IGNITE-4111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670220#comment-16670220
]
Ignite TC Bot commented on IGNITE-4111:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2208611buildTypeId=IgniteTests24Java8_RunAll]
> Communication fails to send message if target node did not finish join process
> --
>
> Key: IGNITE-4111
> URL: https://issues.apache.org/jira/browse/IGNITE-4111
> Project: Ignite
> Issue Type: Bug
> Components: general
>Reporter: Semen Boikov
>Assignee: Amelchev Nikita
>Priority: Minor
> Fix For: 2.8
>
> Attachments: test onFirstMessage hang.log
>
>
> Currently this scenario is possible:
> - joining node sent join request and waits for
> TcpDiscoveryNodeAddFinishedMessage inside ServerImpl.joinTopology
> - others nodes already see this node and can send messages to it (for example
> try to run compute job on this node)
> - joining node can not receive message: TcpCommunicationSpi will hang inside
> 'onFirstMessage' on 'getSpiContext' call, so sending node will get error
> trying to establish connection
> Possible fix: if in onFirstMessage() spi context is not available, then
> TcpCommunicationSpi should send special response which indicates that this
> node is not ready yet, and sender should retry after some time.
> Also need check internal code for places where message can be unnecessarily
> sent to node: one such place is
> GridCachePartitionExchangeManager.refreshPartitions - message is sent to all
> known nodes, but here we can filter by node order / finished exchage version.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670207#comment-16670207
]
PetrovMikhail edited comment on IGNITE-9149 at 10/31/18 3:07 PM:
-
Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-938
PR: https://github.com/apache/ignite/pull/4635
TC:
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F4635%2Fhead
was (Author: petrovmikhail):
Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-938
PR: https://github.com/apache/ignite/pull/4635
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670207#comment-16670207
]
PetrovMikhail commented on IGNITE-9149:
---
Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-938
PR: https://github.com/apache/ignite/pull/4635
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10091) [TC Bot] Replace PR source for autocompleting branch fields
Ryabov Dmitrii created IGNITE-10091: --- Summary: [TC Bot] Replace PR source for autocompleting branch fields Key: IGNITE-10091 URL: https://issues.apache.org/jira/browse/IGNITE-10091 Project: Ignite Issue Type: Task Reporter: Ryabov Dmitrii Assignee: Ryabov Dmitrii Currently, client receive PRs info for autocompletion list separately from the server. Instead, we should get this info from the Bot, because it is cached here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670199#comment-16670199
]
PetrovMikhail commented on IGNITE-9149:
---
All failed tests passe locally.
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9149) Get rid of logging remaining supplier nodes rebalance time
[
https://issues.apache.org/jira/browse/IGNITE-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670197#comment-16670197
]
Ignite TC Bot commented on IGNITE-9149:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 1{color} [[tests
4|https://ci.ignite.apache.org/viewLog.html?buildId=2209820]]
* IgniteCacheQuerySelfTestSuite3:
IgniteCacheContinuousQueryReconnectTest.testReconnectServer - 0,0% fails in
last 100 master runs.
{color:#d04437}Cache (Restarts) 1{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209878]]
* IgniteCacheRestartTestSuite:
GridCachePartitionedNodeRestartTest.testRestartWithPutTenNodesTwoBackups - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209884]]
* IgniteCacheTestSuite4:
CacheStoreUsageMultinodeDynamicStartTxTest.testDynamicStartFromClientWriteBehindStore
- 0,0% fails in last 100 master runs.
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209918buildTypeId=IgniteTests24Java8_RunAll]
> Get rid of logging remaining supplier nodes rebalance time
> --
>
> Key: IGNITE-9149
> URL: https://issues.apache.org/jira/browse/IGNITE-9149
> Project: Ignite
> Issue Type: Task
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: rebalance
>
> Logging rebalance execution time in section of each supplier node have no
> sence and provides no helpfull info for analyzing logs. It also
> overcomplicates {{GridDhtPartitionDemander}}.
> I'm suggesting remove it by simplifying {{Map IgniteDhtDemandedPartitionsMap>>}} to {{Map IgniteDhtDemandedPartitionsMap>}}.
> {code:java}
> /** Remaining. T2: startTime, partitions */
> private final Map> remaining =
> new HashMap<>();
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9394) MVCC: pds corrupted after grid restart.
[ https://issues.apache.org/jira/browse/IGNITE-9394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-9394: Ignite Flags: (was: Docs Required) > MVCC: pds corrupted after grid restart. > --- > > Key: IGNITE-9394 > URL: https://issues.apache.org/jira/browse/IGNITE-9394 > Project: Ignite > Issue Type: Bug > Components: mvcc, persistence >Reporter: Andrew Mashenkov >Priority: Critical > Fix For: 2.7 > > > Ignite fails to apply unfinished checkpoint after restart. See stacktrace > below. > > java.lang.AssertionError: > Assertion error on row: CacheObjectImpl [val=null, > hasValBytes=true]CacheObjectImpl [val=null, hasValBytes=true], expireT > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2286) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.put(BPlusTree.java:2221) > at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.update(IgniteCacheOffheapManagerImpl.java:23 > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.update(GridCacheOffheapManager.java:16 > at > org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.update(IgniteCacheOffheapManagerImpl.java:438) > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyUpdate(GridCacheDatabaseSharedManager.java:24 > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.ja > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1 > at > org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitio > at > org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFutur > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java > at > org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java: > at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.AssertionError > at > org.apache.ignite.internal.processors.cache.tree.AbstractDataLeafIO.storeByOffset(AbstractDataLeafIO.java:67) > at > org.apache.ignite.internal.processors.cache.tree.AbstractDataLeafIO.storeByOffset(AbstractDataLeafIO.java:35) > at > org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.store(BPlusIO.java:183) > at > org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.insert(BPlusIO.java:270) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertSimple(BPlusTree.java:3395) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:3377) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$2500(BPlusTree.java:3257) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:435) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:416) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5594) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5579) > at > org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:346) > at > org.apache.ignite.internal.processors.cache.persistence.DataStructure.write(DataStructure.java:276) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$12300(BPlusTree.java:87) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.tryInsert(BPlusTree.java:3569) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$7600(BPlusTree.java:3257) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putDown(BPlusTree.java:2531) > at > org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2250) > ... 14 more -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9903) Copy only actual amount of data during archiving of WAL segment
[
https://issues.apache.org/jira/browse/IGNITE-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670192#comment-16670192
]
Ignite TC Bot commented on IGNITE-9903:
---
{panel:title=No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2203173buildTypeId=IgniteTests24Java8_RunAll]
> Copy only actual amount of data during archiving of WAL segment
> ---
>
> Key: IGNITE-9903
> URL: https://issues.apache.org/jira/browse/IGNITE-9903
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Alexey Stelmak
>Priority: Major
> Fix For: 2.8
>
>
> Current WAL archiver implementation copies full WAL segment to the archive
> while actual size of the segment can be significantly less then
> {{maxWalSegmentSize}} (segment files are preallocated for max possible
> segment size).
> In order to reduce disk space consuming we need copy only actual data of
> segment using {{SWITCH_SEGMENT_RECORD}} as marker. It will require some kind
> of WAL iterator implementation that will just copy WAL records using
> information about record size without records deserialization.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-7955) MVCC TX: cache peek for key-value API
[ https://issues.apache.org/jira/browse/IGNITE-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov reassigned IGNITE-7955: --- Assignee: Ivan Pavlukhin > MVCC TX: cache peek for key-value API > - > > Key: IGNITE-7955 > URL: https://issues.apache.org/jira/browse/IGNITE-7955 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Alexander Paschenko >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > > We need to implement MVCC-compatible cache peek operation for key-value API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10088) Partition is restored in moving state instead of owning if node restarted before first checkpoint.
[
https://issues.apache.org/jira/browse/IGNITE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10088:
---
Fix Version/s: 2.8
> Partition is restored in moving state instead of owning if node restarted
> before first checkpoint.
> --
>
> Key: IGNITE-10088
> URL: https://issues.apache.org/jira/browse/IGNITE-10088
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Priority: Major
> Fix For: 2.8
>
>
> Reproducer:
> {noformat}
> package org.apache.ignite.internal.processors.cache.transactions;
> import java.util.ArrayList;
> import java.util.List;
> import java.util.Map;
> import java.util.Set;
> import org.apache.ignite.IgniteDataStreamer;
> import org.apache.ignite.IgniteSystemProperties;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cluster.ClusterNode;
> 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.failure.StopNodeFailureHandler;
> import org.apache.ignite.failure.StopNodeOrHaltFailureHandler;
> import org.apache.ignite.internal.IgniteEx;
> import org.apache.ignite.internal.IgniteInternalFuture;
> import org.apache.ignite.internal.TestRecordingCommunicationSpi;
> import org.apache.ignite.internal.managers.communication.GridIoMessage;
> import
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxFinishRequest;
> import
> org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest;
> import org.apache.ignite.internal.processors.cache.verify.IdleVerifyResultV2;
> import org.apache.ignite.internal.util.typedef.T2;
> import org.apache.ignite.lang.IgniteBiPredicate;
> import org.apache.ignite.lang.IgnitePredicate;
> import org.apache.ignite.plugin.extensions.communication.Message;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.GridTestUtils;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import org.apache.ignite.transactions.Transaction;
> import org.apache.ignite.transactions.TransactionConcurrency;
> import org.apache.ignite.transactions.TransactionIsolation;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static org.apache.ignite.configuration.WALMode.LOG_ONLY;
> import static org.apache.ignite.testframework.GridTestUtils.runAsync;
> import static
> org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
> import static
> org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
> /**
> * Test data loss on recovery due to missed partition counter on tx messages
> reorder.
> */
> public class MovingPartitionAfterRestartNoBLTChangeTest extends
> GridCommonAbstractTest {
> /** IP finder. */
> private static final TcpDiscoveryVmIpFinder IP_FINDER = new
> TcpDiscoveryVmIpFinder(true);
> /** */
> private static final int GRID_CNT = 2;
> /** */
> private static final int MB = 1024 * 1024;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> cfg.setConsistentId("node" + igniteInstanceName);
> ((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
> boolean client = igniteInstanceName.startsWith("client");
> cfg.setClientMode(client);
> cfg.setDataStorageConfiguration(new DataStorageConfiguration().
> setWalSegmentSize(12 *
> MB).setWalMode(LOG_ONLY).setPageSize(1024).setCheckpointFrequency(100L).
> setDefaultDataRegionConfiguration(new
> DataRegionConfiguration().setPersistenceEnabled(true).
> setInitialSize(100 * MB).setMaxSize(100 * MB)));
> if (!client) {
> CacheConfiguration ccfg = new
> CacheConfiguration(DEFAULT_CACHE_NAME);
> ccfg.setAtomicityMode(TRANSACTIONAL);
> ccfg.setBackups(2);
> ccfg.setWriteSynchronizationMode(FULL_SYNC);
> ccfg.setOnheapCacheEnabled(false);
> ccfg.setAffinity(new RendezvousAffinityFunction(false, 1));
> cfg.setCacheConfiguration(ccfg);
> }
> return cfg;
> }
> /** {@inheritDoc} */
> @Override protected void beforeTest() throws
[jira] [Updated] (IGNITE-7955) MVCC TX: cache peek for key-value API
[ https://issues.apache.org/jira/browse/IGNITE-7955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Ozerov updated IGNITE-7955: Fix Version/s: 2.8 > MVCC TX: cache peek for key-value API > - > > Key: IGNITE-7955 > URL: https://issues.apache.org/jira/browse/IGNITE-7955 > Project: Ignite > Issue Type: Task > Components: cache, mvcc >Reporter: Alexander Paschenko >Assignee: Ivan Pavlukhin >Priority: Major > Fix For: 2.8 > > > We need to implement MVCC-compatible cache peek operation for key-value API. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10088) Partition is restored in moving state instead of owning if node restarted before first checkpoint.
[
https://issues.apache.org/jira/browse/IGNITE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10088:
---
Description:
Reproducer:
{noformat}
package org.apache.ignite.internal.processors.cache.transactions;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
import java.util.Set;
import org.apache.ignite.IgniteDataStreamer;
import org.apache.ignite.IgniteSystemProperties;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
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.failure.StopNodeFailureHandler;
import org.apache.ignite.failure.StopNodeOrHaltFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import org.apache.ignite.internal.managers.communication.GridIoMessage;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxFinishRequest;
import
org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest;
import org.apache.ignite.internal.processors.cache.verify.IdleVerifyResultV2;
import org.apache.ignite.internal.util.typedef.T2;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.lang.IgnitePredicate;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
import static org.apache.ignite.configuration.WALMode.LOG_ONLY;
import static org.apache.ignite.testframework.GridTestUtils.runAsync;
import static org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
import static
org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
/**
* Test data loss on recovery due to missed partition counter on tx messages
reorder.
*/
public class MovingPartitionAfterRestartNoBLTChangeTest extends
GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** */
private static final int GRID_CNT = 2;
/** */
private static final int MB = 1024 * 1024;
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setConsistentId("node" + igniteInstanceName);
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
cfg.setDataStorageConfiguration(new DataStorageConfiguration().
setWalSegmentSize(12 *
MB).setWalMode(LOG_ONLY).setPageSize(1024).setCheckpointFrequency(100L).
setDefaultDataRegionConfiguration(new
DataRegionConfiguration().setPersistenceEnabled(true).
setInitialSize(100 * MB).setMaxSize(100 * MB)));
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(2);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
ccfg.setAffinity(new RendezvousAffinityFunction(false, 1));
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();
cleanPersistenceDir();
}
/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
super.afterTest();
stopAllGrids();
cleanPersistenceDir();
}
public void testMoving() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
awaitPartitionMapExchange();
stopGrid(1);
awaitPartitionMapExchange();
startGrid(1); // Will trigger rebalance
awaitPartitionMapExchange();
}
}
{noformat}
was:
Reproducer:
{noformat}
[jira] [Updated] (IGNITE-10088) Partition is restored in moving state instead of owning if node restarted before first checkpoint.
[
https://issues.apache.org/jira/browse/IGNITE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10088:
---
Description:
Reproducer:
{noformat}
package org.apache.ignite.internal.processors.cache.transactions;
import java.util.ArrayList;
import java.util.List;
import java.util.Map;
import java.util.Set;
import org.apache.ignite.IgniteDataStreamer;
import org.apache.ignite.IgniteSystemProperties;
import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
import org.apache.ignite.cluster.ClusterNode;
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.failure.StopNodeFailureHandler;
import org.apache.ignite.failure.StopNodeOrHaltFailureHandler;
import org.apache.ignite.internal.IgniteEx;
import org.apache.ignite.internal.IgniteInternalFuture;
import org.apache.ignite.internal.TestRecordingCommunicationSpi;
import org.apache.ignite.internal.managers.communication.GridIoMessage;
import
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxFinishRequest;
import
org.apache.ignite.internal.processors.cache.persistence.db.wal.IgniteWalRebalanceTest;
import org.apache.ignite.internal.processors.cache.verify.IdleVerifyResultV2;
import org.apache.ignite.internal.util.typedef.T2;
import org.apache.ignite.lang.IgniteBiPredicate;
import org.apache.ignite.lang.IgnitePredicate;
import org.apache.ignite.plugin.extensions.communication.Message;
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
import org.apache.ignite.testframework.GridTestUtils;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
import org.apache.ignite.transactions.Transaction;
import org.apache.ignite.transactions.TransactionConcurrency;
import org.apache.ignite.transactions.TransactionIsolation;
import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
import static org.apache.ignite.configuration.WALMode.LOG_ONLY;
import static org.apache.ignite.testframework.GridTestUtils.runAsync;
import static org.apache.ignite.transactions.TransactionConcurrency.PESSIMISTIC;
import static
org.apache.ignite.transactions.TransactionIsolation.REPEATABLE_READ;
/**
* Test data loss on recovery due to missed partition counter on tx messages
reorder.
*/
public class TxMissedPartitionCounterTest extends GridCommonAbstractTest {
/** IP finder. */
private static final TcpDiscoveryVmIpFinder IP_FINDER = new
TcpDiscoveryVmIpFinder(true);
/** */
private static final int GRID_CNT = 2;
/** */
private static final int MB = 1024 * 1024;
/** {@inheritDoc} */
@Override protected IgniteConfiguration getConfiguration(String
igniteInstanceName) throws Exception {
IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
cfg.setConsistentId("node" + igniteInstanceName);
((TcpDiscoverySpi)cfg.getDiscoverySpi()).setIpFinder(IP_FINDER);
boolean client = igniteInstanceName.startsWith("client");
cfg.setClientMode(client);
cfg.setDataStorageConfiguration(new DataStorageConfiguration().
setWalSegmentSize(12 *
MB).setWalMode(LOG_ONLY).setPageSize(1024).setCheckpointFrequency(100L).
setDefaultDataRegionConfiguration(new
DataRegionConfiguration().setPersistenceEnabled(true).
setInitialSize(100 * MB).setMaxSize(100 * MB)));
if (!client) {
CacheConfiguration ccfg = new
CacheConfiguration(DEFAULT_CACHE_NAME);
ccfg.setAtomicityMode(TRANSACTIONAL);
ccfg.setBackups(2);
ccfg.setWriteSynchronizationMode(FULL_SYNC);
ccfg.setOnheapCacheEnabled(false);
ccfg.setAffinity(new RendezvousAffinityFunction(false, 1));
cfg.setCacheConfiguration(ccfg);
}
return cfg;
}
/** {@inheritDoc} */
@Override protected void beforeTest() throws Exception {
super.beforeTest();
cleanPersistenceDir();
}
/** {@inheritDoc} */
@Override protected void afterTest() throws Exception {
super.afterTest();
stopAllGrids();
cleanPersistenceDir();
}
public void testMoving() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
awaitPartitionMapExchange();
stopGrid(1);
awaitPartitionMapExchange();
startGrid(1); // Will trigger rebalance
awaitPartitionMapExchange();
}
}
{noformat}
was:
Reproducer:
{noformat}
public void
[jira] [Updated] (IGNITE-10088) Partition is restored in moving state instead of owning if node restarted before first checkpoint.
[
https://issues.apache.org/jira/browse/IGNITE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10088:
---
Description:
Reproducer:
{noformat}
public void testMoving() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
awaitPartitionMapExchange();
stopGrid(1);
awaitPartitionMapExchange();
startGrid(1);
awaitPartitionMapExchange();
}
{noformat}
was:
Scenario:
1. Start grid with large enough checkpoint freq, wait for rebalance, put some
data.
2. Observe all partitions in OWNING state.
3. Kill of trigger FH for node before checkpoint is started.
4. Return node to grid, observe all partitions created with moving state and
unnecessary rebalanced.
Problem in
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#restorePartitionStates
which doesn't apply owning partition state.
{noformat}
public void testMoving() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
awaitPartitionMapExchange();
stopGrid(1);
awaitPartitionMapExchange();
startGrid(1);
awaitPartitionMapExchange();
}
{noformat}
> Partition is restored in moving state instead of owning if node restarted
> before first checkpoint.
> --
>
> Key: IGNITE-10088
> URL: https://issues.apache.org/jira/browse/IGNITE-10088
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Priority: Major
>
> Reproducer:
> {noformat}
> public void testMoving() throws Exception {
> IgniteEx crd = startGrid(0);
> startGrid(1);
> crd.cluster().active(true);
> awaitPartitionMapExchange();
> stopGrid(1);
> awaitPartitionMapExchange();
> startGrid(1);
> awaitPartitionMapExchange();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-10088) Partition is restored in moving state instead of owning if node restarted before first checkpoint.
[
https://issues.apache.org/jira/browse/IGNITE-10088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-10088:
---
Summary: Partition is restored in moving state instead of owning if node
restarted before first checkpoint. (was: Partition can be restored in moving
state instead of owning if node crashed before first checkpoint.)
> Partition is restored in moving state instead of owning if node restarted
> before first checkpoint.
> --
>
> Key: IGNITE-10088
> URL: https://issues.apache.org/jira/browse/IGNITE-10088
> Project: Ignite
> Issue Type: Bug
>Reporter: Alexei Scherbakov
>Priority: Major
>
> Scenario:
> 1. Start grid with large enough checkpoint freq, wait for rebalance, put some
> data.
> 2. Observe all partitions in OWNING state.
> 3. Kill of trigger FH for node before checkpoint is started.
> 4. Return node to grid, observe all partitions created with moving state and
> unnecessary rebalanced.
> Problem in
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#restorePartitionStates
> which doesn't apply owning partition state.
> {noformat}
> public void testMoving() throws Exception {
> IgniteEx crd = startGrid(0);
> startGrid(1);
> crd.cluster().active(true);
> awaitPartitionMapExchange();
> stopGrid(1);
> awaitPartitionMapExchange();
> startGrid(1);
> awaitPartitionMapExchange();
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-9850) Python thin: Find out the cause of the python's client low performance
[ https://issues.apache.org/jira/browse/IGNITE-9850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670167#comment-16670167 ] Pavel Petroshenko edited comment on IGNITE-9850 at 10/31/18 2:27 PM: - What has been done: # Profiling the python Thin Client on the standard cpython VM # Based on the profiling results, a bottleneck with the package imports was found. Performance of the Python Thin Client is comparable with that of the Node.JS now # The found bottleneck has been fixed and merged to master # Implemented an optimization for caching the read data (to minimize the number of socket reads), which didn't give any reasonable gain in performance, so it doesn't make sense to integrate it at this point. Just for our records, the change is made here: https://github.com/nobitlost/ignite/commit/c9e5686a0c6df235c8aec03df27c3a6fd84654e2 # So there is no room for further performance improvements as far as I can see Reasons why Python is slower than other clients: # The cpython VM has no dynamic or JIT compiler, it's a purely interpreted language implementation (for example turning the HotSpot compiler in Java itself makes it at least 2+ times slower) # Python is a natively single-threaded language by nature, while other languages can perform some blocking operations (including io) asynchronously on dedicated threads (specific to internal VM and system libraries implementation) # The VMs have different runtime (scheduler, garbage collector, interpreter) implementations. Some of them are manually optimized for a specific platform, some are not. So given that we can clearly explain the difference and the performance of the Python client is comparable to Node.JS I suggest closing this issue as resolved. was (Author: pavel.petroshenko): What has been done: # Profiling the python Thin Client on the standard cpython VM # Based on the profiling results, a bottleneck with the package imports was found. Performance of the Python Thin Client is comparable with that of the Node.JS now # The found bottleneck has been fixed and merged to master # Implemented an optimization for caching the read data (to minimize the number of socket reads), which didn't give any reasonable gain in performance, so it doesn't make sense to integrate it at this point # So there is no room for further performance improvements as far as I can see Reasons why Python is slower than other clients: # The cpython VM has no dynamic or JIT compiler, it's a purely interpreted language implementation (for example turning the HotSpot compiler in Java itself makes it at least 2+ times slower) # Python is a natively single-threaded language by nature, while other languages can perform some blocking operations (including io) asynchronously on dedicated threads (specific to internal VM and system libraries implementation) # The VMs have different runtime (scheduler, garbage collector, interpreter) implementations. Some of them are manually optimized for a specific platform, some are not. So given that we can clearly explain the difference and the performance of the Python client is comparable to Node.JS I suggest closing this issue as resolved. > Python thin: Find out the cause of the python's client low performance > -- > > Key: IGNITE-9850 > URL: https://issues.apache.org/jira/browse/IGNITE-9850 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Dmitry Melnichuk >Priority: Critical > Labels: python > Fix For: 2.8 > > > According to benchmarks results reported by IGNITE-9824, python thin client > is 3 to 4 times slower than Java client. We need to find out the root cause > of this and if we can fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9679) Document critical workers liveness checking implementation
[
https://issues.apache.org/jira/browse/IGNITE-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670176#comment-16670176
]
Artem Budnikov commented on IGNITE-9679:
[~pgarg] please review the page.
> Document critical workers liveness checking implementation
> --
>
> Key: IGNITE-9679
> URL: https://issues.apache.org/jira/browse/IGNITE-9679
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Andrey Kuznetsov
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.7
>
>
> Newly implemented critical worker thread liveness checks should be mentioned
> in Ignite Documentation. Brief description of the functionality follows.
> Ignite node has a number of critical worker threads that should be alive and
> responsive, otherwise node's health is not guaranteed. These threads monitor
> each other periodically and track two aspects for a thread being checked:
> - whether it's alive;
> - whether it updates its internal heartbeat timestamp.
> Whenever at least one of the above conditions is violated, checker thread
> logs the error and calls currently configured {{FailureHandler}}.
> {{IgniteConfiguration.SystemWorkerBlockedTimeout}} configuration property
> affects monitoring behavior. At runtime monitoring settings can be changed
> via {{FailureHandlingMxBean}}.
> By default, liveness checks are enabled, but blocked system worker detection
> will not lead to failure handler invocation, see
> {{FailureProcessor#getDefaultFailureHandler}} .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (IGNITE-9679) Document critical workers liveness checking implementation
[
https://issues.apache.org/jira/browse/IGNITE-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Budnikov reassigned IGNITE-9679:
--
Assignee: Prachi Garg (was: Andrey Kuznetsov)
> Document critical workers liveness checking implementation
> --
>
> Key: IGNITE-9679
> URL: https://issues.apache.org/jira/browse/IGNITE-9679
> Project: Ignite
> Issue Type: Task
> Components: documentation
>Reporter: Andrey Kuznetsov
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.7
>
>
> Newly implemented critical worker thread liveness checks should be mentioned
> in Ignite Documentation. Brief description of the functionality follows.
> Ignite node has a number of critical worker threads that should be alive and
> responsive, otherwise node's health is not guaranteed. These threads monitor
> each other periodically and track two aspects for a thread being checked:
> - whether it's alive;
> - whether it updates its internal heartbeat timestamp.
> Whenever at least one of the above conditions is violated, checker thread
> logs the error and calls currently configured {{FailureHandler}}.
> {{IgniteConfiguration.SystemWorkerBlockedTimeout}} configuration property
> affects monitoring behavior. At runtime monitoring settings can be changed
> via {{FailureHandlingMxBean}}.
> By default, liveness checks are enabled, but blocked system worker detection
> will not lead to failure handler invocation, see
> {{FailureProcessor#getDefaultFailureHandler}} .
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-10079) FileWriteAheadLogManager may return invalid lastCompactedSegment
[
https://issues.apache.org/jira/browse/IGNITE-10079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670171#comment-16670171
]
Anton Kalashnikov commented on IGNITE-10079:
[~andrey-kuznetsov], I will take a look your changes in nearest time.
> FileWriteAheadLogManager may return invalid lastCompactedSegment
>
>
> Key: IGNITE-10079
> URL: https://issues.apache.org/jira/browse/IGNITE-10079
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: WalCompactionAfterRestartTest.java
>
>
> As of current {{master}} branch,
> {{FileWriteAheadLogManager#lastCompactedSegment}} may report -1 even after
> some segments have been actually compressed. Reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9850) Python thin: Find out the cause of the python's client low performance
[ https://issues.apache.org/jira/browse/IGNITE-9850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670167#comment-16670167 ] Pavel Petroshenko commented on IGNITE-9850: --- What has been done: # Profiling the python Thin Client on the standard cpython VM # Based on the profiling results, a bottleneck with the package imports was found. Performance of the Python Thin Client is comparable with that of the Node.JS now # The found bottleneck has been fixed and merged to master # Implemented an optimization for caching the read data (to minimize the number of socket reads), which didn't give any reasonable gain in performance, so it doesn't make sense to integrate it at this point # So there is no room for further performance improvements as far as I can see Reasons why Python is slower than other clients: # The cpython VM has no dynamic or JIT compiler, it's a purely interpreted language implementation (for example turning the HotSpot compiler in Java itself makes it at least 2+ times slower) # Python is a natively single-threaded language by nature, while other languages can perform some blocking operations (including io) asynchronously on dedicated threads (specific to internal VM and system libraries implementation) # The VMs have different runtime (scheduler, garbage collector, interpreter) implementations. Some of them are manually optimized for a specific platform, some are not. So given that we can clearly explain the difference and the performance of the Python client is comparable to Node.JS I suggest closing this issue as resolved. > Python thin: Find out the cause of the python's client low performance > -- > > Key: IGNITE-9850 > URL: https://issues.apache.org/jira/browse/IGNITE-9850 > Project: Ignite > Issue Type: Task > Components: thin client >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Dmitry Melnichuk >Priority: Critical > Labels: python > Fix For: 2.8 > > > According to benchmarks results reported by IGNITE-9824, python thin client > is 3 to 4 times slower than Java client. We need to find out the root cause > of this and if we can fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (IGNITE-10084) Cache 5 tests optimization
[ https://issues.apache.org/jira/browse/IGNITE-10084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov reassigned IGNITE-10084: -- Assignee: Alexey Platonov (was: Ivan Bessonov) > Cache 5 tests optimization > -- > > Key: IGNITE-10084 > URL: https://issues.apache.org/jira/browse/IGNITE-10084 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Alexey Platonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > We need to investigate how to optimize these tests: > IgniteCacheStarvationOnRebalanceTest.testLoadSystemWithPutAndStartRebalancing > (/) > CacheSerializableTransactionsTest.testGetRemoveTxNearCache2 > CacheSerializableTransactionsTest.testGetRemoveTxNearCache1 > CacheSerializableTransactionsTest.testRandomOperations > CacheSerializableTransactionsTest.testIncrementTxRestart > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart > > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClientsNodeRestart > > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockWithNonSerializable > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockGetPut > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClients > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlock > and optimize them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-10084) Cache 5 tests optimization
[ https://issues.apache.org/jira/browse/IGNITE-10084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Bessonov updated IGNITE-10084: --- Description: We need to investigate how to optimize these tests: IgniteCacheStarvationOnRebalanceTest.testLoadSystemWithPutAndStartRebalancing (/) CacheSerializableTransactionsTest.testGetRemoveTxNearCache2 CacheSerializableTransactionsTest.testGetRemoveTxNearCache1 CacheSerializableTransactionsTest.testRandomOperations CacheSerializableTransactionsTest.testIncrementTxRestart CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClientsNodeRestart CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockWithNonSerializable CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockGetPut CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClients CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlock and optimize them. was: We need to investigate how to optimize these tests: IgniteCacheStarvationOnRebalanceTest.testLoadSystemWithPutAndStartRebalancing CacheSerializableTransactionsTest.testGetRemoveTxNearCache2 CacheSerializableTransactionsTest.testGetRemoveTxNearCache1 CacheSerializableTransactionsTest.testRandomOperations CacheSerializableTransactionsTest.testIncrementTxRestart CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClientsNodeRestart CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockWithNonSerializable CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockGetPut CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClients CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlock and optimize them. > Cache 5 tests optimization > -- > > Key: IGNITE-10084 > URL: https://issues.apache.org/jira/browse/IGNITE-10084 > Project: Ignite > Issue Type: Improvement >Reporter: Ivan Bessonov >Assignee: Ivan Bessonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Fix For: 2.8 > > > We need to investigate how to optimize these tests: > IgniteCacheStarvationOnRebalanceTest.testLoadSystemWithPutAndStartRebalancing > (/) > CacheSerializableTransactionsTest.testGetRemoveTxNearCache2 > CacheSerializableTransactionsTest.testGetRemoveTxNearCache1 > CacheSerializableTransactionsTest.testRandomOperations > CacheSerializableTransactionsTest.testIncrementTxRestart > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart > > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClientsNodeRestart > > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockWithNonSerializable > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockGetPut > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClients > CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlock > and optimize them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670146#comment-16670146
]
PetrovMikhail commented on IGNITE-9312:
---
All failed tests passed locally.
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation
[
https://issues.apache.org/jira/browse/IGNITE-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670136#comment-16670136
]
Ignite TC Bot commented on IGNITE-9312:
---
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209585]]
* IgniteBasicTestSuite: OomFailureHandlerTest.testServiceInvokeOomError - 0,0%
fails in last 100 master runs.
{color:#d04437}Cache 8{color} [[tests
3|https://ci.ignite.apache.org/viewLog.html?buildId=2209615]]
* IgniteCacheTestSuite8: GridCachePreloadingEvictionsSelfTest.testEvictions -
0,0% fails in last 100 master runs.
* IgniteCacheTestSuite8:
GridCacheConcurrentEvictionConsistencySelfTest.testPolicyConsistencyLruLocalFewKeys
- 0,0% fails in last 100 master runs.
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2209556]]
* IgniteHadoopFileSystemClientBasedPrimarySelfTest.testClientReconnect (last
started)
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2209642]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2209645buildTypeId=IgniteTests24Java8_RunAll]
> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
> Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
> Labels: inspections
>
> New `Code Inspections` profile can be found
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}}
> annotation regarding this inscpetion profile.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10090) Fix `redundant type cast` inspections over the whole project code
Maxim Muzafarov created IGNITE-10090:
Summary: Fix `redundant type cast` inspections over the whole
project code
Key: IGNITE-10090
URL: https://issues.apache.org/jira/browse/IGNITE-10090
Project: Ignite
Issue Type: Task
Reporter: Maxim Muzafarov
Fix For: 2.8
We need to fix `redundant type cast` over the whole Apache Ignite project code.
Enable this inspection with 'ERROR' type in
{{idea\ignite_inspections_teamcity.xml}} configuration file.
{code}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild
[ https://issues.apache.org/jira/browse/IGNITE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670124#comment-16670124 ] ASF GitHub Bot commented on IGNITE-8719: GitHub user antonovsergey93 opened a pull request: https://github.com/apache/ignite/pull/5223 IGNITE-8719 Store information about starting of index rebuild. You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8719 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/5223.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 #5223 commit cfbd9ba1cc7c31fbe43bdd2e00bad81c8396a464 Author: Sergey Antonov Date: 2018-10-30T09:04:33Z IGNITE-8719 Try reproduce problem. commit b0c5d2740f9aa1814b6809ac7ad11b09d5d53250 Author: Sergey Antonov Date: 2018-10-31T13:34:11Z IGNITE-8719 First version of fix. > Index left partially built if a node crashes during index create or rebuild > --- > > Key: IGNITE-8719 > URL: https://issues.apache.org/jira/browse/IGNITE-8719 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Sergey Antonov >Priority: Critical > Fix For: 2.8 > > Attachments: IndexRebuildAfterNodeCrashTest.java, > IndexRebuildingTest.java > > > Currently, we do not have any state associated with the index tree. Consider > the following scenario: > 1) Start node, put some data > 2) start CREATE INDEX operation > 3) Wait for a checkpoint and stop node before index create finished > 4) Restart node > Since the checkpoint finished, the new index tree will be persisted to the > disk, but not all data will be present in the index. > We should somehow store information about initializing index tree and mark it > valid only after all data is indexed. The state should be persisted as well. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10089) Web Console: Implement debug logging and allow to enable it at runtime
Alexey Kuznetsov created IGNITE-10089: - Summary: Web Console: Implement debug logging and allow to enable it at runtime Key: IGNITE-10089 URL: https://issues.apache.org/jira/browse/IGNITE-10089 Project: Ignite Issue Type: Improvement Components: wizards Reporter: Alexey Kuznetsov Assignee: Alexey Kuznetsov We need some kind of debugging of key functionality (especially AgentManager). And we can have a kind of "Options screen" to enable / disable this mode. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-10048) Bounded iteration in standalone WAL iterator with compaction enabled may skip records
[
https://issues.apache.org/jira/browse/IGNITE-10048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16670079#comment-16670079
]
Ignite TC Bot commented on IGNITE-10048:
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Binary Objects (Simple Mapper Basic){color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=2209805]]
* IgniteBinarySimpleNameMapperBasicTestSuite:
GridEventConsumeSelfTest.testRemoteProjection - 0,0% fails in last 100 master
runs.
{color:#d04437}PDS 2{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=2209924]]
* IgnitePdsTestSuite2: IgniteWalIteratorExceptionDuringReadTest.test - 0,0%
fails in last 100 master runs.
{color:#d04437}PDS (Direct IO) 2{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=2209920]]
{panel}
[TeamCity Run All
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2193103buildTypeId=IgniteTests24Java8_RunAll]
> Bounded iteration in standalone WAL iterator with compaction enabled may skip
> records
> -
>
> Key: IGNITE-10048
> URL: https://issues.apache.org/jira/browse/IGNITE-10048
> Project: Ignite
> Issue Type: Improvement
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Major
> Fix For: 2.8
>
>
> Bounded iteration with non-zero start/end offsets may skip some records in
> intermediate segments. Reproducer (wal compaction should be enabled):
> {noformat}
> /**
> *
> */
> public void testBoundedIterationOverSeveralSegments() throws Exception {
> walCompactionEnabled = true;
> IgniteEx ig = (IgniteEx)startGrid();
> String archiveWalDir = getArchiveWalDirPath(ig);
> ig.cluster().active(true);
> IgniteCache cache = ig.getOrCreateCache(
> new CacheConfiguration<>().setName("c-n").setAffinity(new
> RendezvousAffinityFunction(false, 32)));
> IgniteCacheDatabaseSharedManager sharedMgr =
> ig.context().cache().context().database();
> IgniteWriteAheadLogManager walMgr =
> ig.context().cache().context().wal();
> WALPointer fromPtr = null;
> int recordsCnt = WAL_SEGMENT_SIZE / 8 /* record size */ * 5;
> for (int i = 0; i < recordsCnt; i++) {
> WALPointer ptr = walMgr.log(new PartitionDestroyRecord(i, i));
> if (i == 100)
> fromPtr = ptr;
> }
> assertNotNull(fromPtr);
> cache.put(1, 1);
> forceCheckpoint();
> // Generate WAL segments for filling WAL archive folder.
> for (int i = 0; i < 2 *
> ig.configuration().getDataStorageConfiguration().getWalSegments(); i++) {
> sharedMgr.checkpointReadLock();
> try {
> walMgr.log(new SnapshotRecord(i, false),
> RolloverType.NEXT_SEGMENT);
> }
> finally {
> sharedMgr.checkpointReadUnlock();
> }
> }
> cache.put(2, 2);
> forceCheckpoint();
> U.sleep(5000);
> stopGrid();
> WALIterator it = new IgniteWalIteratorFactory(log)
> .iterator(new
> IteratorParametersBuilder().from((FileWALPointer)fromPtr).filesOrDirs(archiveWalDir));
> TreeSet foundCounters = new TreeSet<>();
> it.forEach(x -> {
> WALRecord rec = x.get2();
> if (rec instanceof PartitionDestroyRecord)
> foundCounters.add(((WalRecordCacheGroupAware)rec).groupId());
> });
> assertEquals(new Integer(100), foundCounters.first());
> assertEquals(new Integer(recordsCnt - 1), foundCounters.last());
> assertEquals(recordsCnt - 100, foundCounters.size());
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10088) Partition can be restored in moving state instead of owning if node crashed before first checkpoint.
Alexei Scherbakov created IGNITE-10088:
--
Summary: Partition can be restored in moving state instead of
owning if node crashed before first checkpoint.
Key: IGNITE-10088
URL: https://issues.apache.org/jira/browse/IGNITE-10088
Project: Ignite
Issue Type: Bug
Reporter: Alexei Scherbakov
Scenario:
1. Start grid with large enough checkpoint freq, wait for rebalance, put some
data.
2. Observe all partitions in OWNING state.
3. Kill of trigger FH for node before checkpoint is started.
4. Return node to grid, observe all partitions created with moving state and
unnecessary rebalanced.
Problem in
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager#restorePartitionStates
which doesn't apply owning partition state.
{noformat}
public void testMoving() throws Exception {
IgniteEx crd = startGrid(0);
startGrid(1);
crd.cluster().active(true);
awaitPartitionMapExchange();
stopGrid(1);
awaitPartitionMapExchange();
startGrid(1);
awaitPartitionMapExchange();
}
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9612) Improve checkpoint mark phase speed.
[
https://issues.apache.org/jira/browse/IGNITE-9612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexei Scherbakov updated IGNITE-9612:
--
Ignite Flags: (was: Docs Required)
> Improve checkpoint mark phase speed.
>
>
> Key: IGNITE-9612
> URL: https://issues.apache.org/jira/browse/IGNITE-9612
> Project: Ignite
> Issue Type: Improvement
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>Priority: Major
> Fix For: 2.7
>
>
> I'm observing regular slow checkpoints due to long mark duration, which is
> not related to dirty pages number:
> {noformat}
> 2018-09-01 14:55:20.408 [INFO
> ][db-checkpoint-thread-#241%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=01e0c7bf-842f-4ed6-8589-b4904063434f,
> startPtr=FileWALPointer [idx=19814, fileOff=948996096, len=5233457],
> checkpointLockWait=0ms, checkpointLockHoldTime=951ms,
> walCpRecordFsyncDuration=39ms, pages=78477, reason='timeout']
> 2018-09-01 14:55:21.307 [INFO
> ][db-checkpoint-thread-#241%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Checkpoint finished [cpId=01e0c7bf-842f-4ed6-8589-b4904063434f, pages=78477,
> markPos=FileWALPointer [idx=19814, fileOff=948996096, len=5233457],
> walSegmentsCleared=0, walSegmentsCovered=[], *markDuration=1002m*s,
> pagesWrite=478ms, fsync=421ms, total=1901ms]
> {noformat}
> {noformat}
> 2018-09-01 14:58:20.355 [INFO
> ][db-checkpoint-thread-#241%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Checkpoint started [checkpointId=09d1f4bc-d3f3-4a16-b291-89d7fa745ea5,
> startPtr=FileWALPointer [idx=19814, fileOff=124208, len=5233457],
> checkpointLockWait=0ms, checkpointLockHoldTime=926ms,
> walCpRecordFsyncDuration=14ms, pages=10837, reason='timeout']
> 2018-09-01 14:58:20.480 [INFO
> ][db-checkpoint-thread-#241%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.p.GridCacheDatabaseSharedManager]
> Checkpoint finished [cpId=09d1f4bc-d3f3-4a16-b291-89d7fa745ea5, pages=10837,
> markPos=FileWALPointer [idx=19814, fileOff=124208, len=5233457],
> walSegmentsCleared=0, walSegmentsCovered=[], *markDuration=943ms*,
> pagesWrite=64ms, fsync=61ms, total=1068ms]
> {noformat}
> Debugging has revealed what this is due to large amount of work required to
> save metadata for metapages and free/reuse lists. Because this is done under
> checkpoint write lock, all other activities are blocked, resulting in
> increased tx and atomic ops latency.
> Simple solution: parallelize metadata processing during mark phase.
> Best way to solve the problem is described in IGNITE-9520.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-9147) Race between tx async rollback and lock mapping on near node can produce hanging primary tx
[ https://issues.apache.org/jira/browse/IGNITE-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexei Scherbakov updated IGNITE-9147: -- Ignite Flags: (was: Docs Required) > Race between tx async rollback and lock mapping on near node can produce > hanging primary tx > --- > > Key: IGNITE-9147 > URL: https://issues.apache.org/jira/browse/IGNITE-9147 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 2.5 >Reporter: ARomantsov >Assignee: Alexei Scherbakov >Priority: Critical > Fix For: 2.7 > > > I ran a simple test > 1) Start 15 servers node > 2) Start client with long transaction > 3) Additional start 5 client with loading in many caches (near 2 thousand) > 4) Stop 1 server node, wait 1 minute and start it back > Cluster freenze on more than hour -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10087) IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 is flaky in master
Amelchev Nikita created IGNITE-10087: Summary: IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 is flaky in master Key: IGNITE-10087 URL: https://issues.apache.org/jira/browse/IGNITE-10087 Project: Ignite Issue Type: Bug Reporter: Amelchev Nikita Assignee: Amelchev Nikita Fix For: 2.8 The IgniteClientReconnectMassiveShutdownTest.testMassiveServersShutdown1 test is flaky in master. Sometimes the test fails on test timeout (5 min). [Test history.|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-6728945354254258306==testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
