[jira] [Commented] (IGNITE-6796) GridClusterStateProcessor$5 has no @GridInternal annotation
[
https://issues.apache.org/jira/browse/IGNITE-6796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892231#comment-16892231
]
Ignite TC Bot commented on IGNITE-6796:
---
{panel:title=Branch: [pull/6720/head] Base: [master] : Possible Blockers
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4390800]]
{color:#d04437}[Licenses Headers]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4390801]]
{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4388335buildTypeId=IgniteTests24Java8_RunAll]
> GridClusterStateProcessor$5 has no @GridInternal annotation
> ---
>
> Key: IGNITE-6796
> URL: https://issues.apache.org/jira/browse/IGNITE-6796
> Project: Ignite
> Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Alexander Korenshteyn
>Priority: Trivial
> Time Spent: 20m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Reopened] (IGNITE-3897) Test transactional behaviour of caches during rolling restart
[ https://issues.apache.org/jira/browse/IGNITE-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov reopened IGNITE-3897: [~glukos], could you please take a look? John has replied to all comments, so I guess we should consider merging the change. > Test transactional behaviour of caches during rolling restart > - > > Key: IGNITE-3897 > URL: https://issues.apache.org/jira/browse/IGNITE-3897 > Project: Ignite > Issue Type: Test > Components: cache >Affects Versions: 1.7 >Reporter: John Levey >Assignee: John Levey >Priority: Major > > Create a test that validates the following conditions against a running > cluster that is undergoing a rolling restart: > * Validate a continuous aggregate sum against the cluster during restarts > * Validate transaction handling against the cluster during restarts > See also https://issues.apache.org/jira/browse/IGNITE-3456 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12011) MetricUpdater timeout can't be configured
Max Shonichev created IGNITE-12011:
--
Summary: MetricUpdater timeout can't be configured
Key: IGNITE-12011
URL: https://issues.apache.org/jira/browse/IGNITE-12011
Project: Ignite
Issue Type: Bug
Affects Versions: 3.0
Reporter: Max Shonichev
Fix For: 3.0
{noformat}
/** Metrics update frequency. */
private static final long METRICS_UPDATE_FREQ = 3000;
...
/** {@inheritDoc} */
@Override protected void onKernalStart0() throws IgniteCheckedException {
metricsUpdateTask = ctx.timeout().schedule(new MetricsUpdater(),
METRICS_UPDATE_FREQ, METRICS_UPDATE_FREQ);
}
{noformat}
Would be great if metric updater timeout was externally configured.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (IGNITE-11027) CPP: Add support of compact footer for C++
[ https://issues.apache.org/jira/browse/IGNITE-11027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin reassigned IGNITE-11027: Assignee: Vyacheslav Koptilin > CPP: Add support of compact footer for C++ > -- > > Key: IGNITE-11027 > URL: https://issues.apache.org/jira/browse/IGNITE-11027 > Project: Ignite > Issue Type: Improvement > Components: platforms >Affects Versions: 2.7 >Reporter: Igor Sapego >Assignee: Vyacheslav Koptilin >Priority: Major > > Currently, compact footers are not supported by Ignite C++ and C++ thin > clients. As they both share the same library - binary, we can add this > support for both C++ thin and Ignite C++ at the same time. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12004) CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields is flaky
[ https://issues.apache.org/jira/browse/IGNITE-12004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891953#comment-16891953 ] Ivan Pavlukhin commented on IGNITE-12004: - Rerun a suite containing a changed test class https://ci.ignite.apache.org/viewLog.html?buildId=4387614=IgniteTests24Java8_Queries2 > CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields is flaky > -- > > Key: IGNITE-12004 > URL: https://issues.apache.org/jira/browse/IGNITE-12004 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.7.5 >Reporter: Ivan Pavlukhin >Assignee: Ivan Pavlukhin >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields fails often > https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4227647830422954979=testDetails -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12007) Latest "apacheignite/web-console-backend" docker image is broken
[
https://issues.apache.org/jira/browse/IGNITE-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891941#comment-16891941
]
Dmitriy Pavlov commented on IGNITE-12007:
-
[~ezhuravl], WC was a 3rd party image prepared by someone, and AFAIK the
community didn't accept it. If I'm wrong, please share vote thread with adding
WC to release.
Would you volunteer to discuss it with community, prepare release docs and DIY?
if yes, we can reopen.
Since I was the release manager for 2.7.5 I removed this requirement from the
release procedure. So since the image is not shipped as part of the release, I
see no reason to fix bugs in it.
> Latest "apacheignite/web-console-backend" docker image is broken
>
>
> Key: IGNITE-12007
> URL: https://issues.apache.org/jira/browse/IGNITE-12007
> Project: Ignite
> Issue Type: Bug
> Components: UI
>Affects Versions: 2.7
>Reporter: Igor Belyakov
>Priority: Critical
>
> It's not possible to run docker container by using the latest version of
> "apacheignite/web-console-backend" image.
> Next error happens on the start:
> {code:java}
> npm ERR! A complete log of this run can be found in:
> npm ERR! /root/.npm/_logs/2019-07-23T14_24_40_353Z-debug.log
> npm ERR! path /opt/web-console/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/opt/web-console/package.json'
> npm ERR! enoent This is related to npm not being able to find a file.
> npm ERR! enoent{code}
> How to reproduce:
> Run container by using docker-compose as described here:
> [https://hub.docker.com/r/apacheignite/web-console-backend]
>
> Seems like it was broken by the next commit:
> [https://github.com/apache/ignite/commit/4c295f8f468ddfce458948c17c13b1748b13e918#diff-ec0d595d738c4207e08ce210624e902aR22]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-12006) Threads may be parked for indefinite time during throttling after spurious wakeups
[
https://issues.apache.org/jira/browse/IGNITE-12006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891900#comment-16891900
]
Sergey Antonov commented on IGNITE-12006:
-
[~v.pyatkov] Could your review my changes?
> Threads may be parked for indefinite time during throttling after spurious
> wakeups
> --
>
> Key: IGNITE-12006
> URL: https://issues.apache.org/jira/browse/IGNITE-12006
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the log we see the following behavior:
> {noformat}
> 2019-07-04 06:29:03.649[WARN
> ][sys-#328%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#328%NODE%xyzGridNodeName% for timeout(ms)=16335
> 2019-07-04 06:29:03.649[WARN
> ][sys-#326%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#326%NODE%xyzGridNodeName% for timeout(ms)=13438
> 2019-07-04 06:29:03.649[WARN
> ][sys-#277%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#277%NODE%xyzGridNodeName% for timeout(ms)=11609
> 2019-07-04 06:29:03.649[WARN
> ][sys-#331%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#331%NODE%xyzGridNodeName% for timeout(ms)=18009
> 2019-07-04 06:29:03.649[WARN
> ][sys-#321%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#321%NODE%xyzGridNodeName% for timeout(ms)=15557
> 2019-07-04 06:29:03.650[WARN
> ][sys-#307%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#307%NODE%xyzGridNodeName% for timeout(ms)=27938
> 2019-07-04 06:29:03.649[WARN
> ][sys-#316%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#316%NODE%xyzGridNodeName% for timeout(ms)=12189
> 2019-07-04 06:29:03.649[WARN
> ][sys-#311%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#311%NODE%xyzGridNodeName% for timeout(ms)=11056
> 2019-07-04 06:29:03.650[WARN
> ][sys-#295%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#295%NODE%xyzGridNodeName% for timeout(ms)=20848
> 2019-07-04 06:29:03.649[WARN
> ][sys-#290%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#290%NODE%xyzGridNodeName% for timeout(ms)=14816
> 2019-07-04 06:29:03.649[WARN
> ][sys-#332%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#332%NODE%xyzGridNodeName% for timeout(ms)=14110
> 2019-07-04 06:29:03.649[WARN
> ][sys-#298%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#298%NODE%xyzGridNodeName% for timeout(ms)=10028
> 2019-07-04 06:29:03.650[WARN
> ][sys-#304%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#304%NODE%xyzGridNodeName% for timeout(ms)=19855
> 2019-07-04 06:29:03.650[WARN
> ][sys-#331%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#331%NODE%xyzGridNodeName% for timeout(ms)=41277
> 2019-07-04 06:29:03.650[WARN
> ][sys-#291%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#291%NODE%xyzGridNodeName% for timeout(ms)=17151
> 2019-07-04 06:29:03.650[WARN
> ][sys-#308%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#308%NODE%xyzGridNodeName% for timeout(ms)=39312
> 2019-07-04 06:29:03.650[WARN
> ][sys-#322%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#322%NODE%xyzGridNodeName% for timeout(ms)=43341
> 2019-07-04 06:29:03.650[WARN
> ][sys-#306%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#306%NODE%xyzGridNodeName% for timeout(ms)=21890
> 2019-07-04 06:29:03.650[WARN
> ][sys-#315%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#315%NODE%xyzGridNodeName% for timeout(ms)=18909
> 2019-07-04 06:29:03.650[WARN
> ][sys-#321%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#321%NODE%xyzGridNodeName% for timeout(ms)=74129
> 2019-07-04 06:29:03.650[WARN
> ][sys-#305%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#305%NODE%xyzGridNodeName% for timeout(ms)=26608
> 2019-07-04 06:29:03.650[WARN
> ][sys-#309%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#309%NODE%xyzGridNodeName% for timeout(ms)=77835
> 2019-07-04 06:29:03.650[WARN
> ][sys-#291%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#291%NODE%xyzGridNodeName% for timeout(ms)=90104
> 2019-07-04 06:29:03.650[WARN
>
[jira] [Commented] (IGNITE-12006) Threads may be parked for indefinite time during throttling after spurious wakeups
[
https://issues.apache.org/jira/browse/IGNITE-12006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891897#comment-16891897
]
Ignite TC Bot commented on IGNITE-12006:
{panel:title=Branch: [pull/6712/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4380398buildTypeId=IgniteTests24Java8_RunAll]
> Threads may be parked for indefinite time during throttling after spurious
> wakeups
> --
>
> Key: IGNITE-12006
> URL: https://issues.apache.org/jira/browse/IGNITE-12006
> Project: Ignite
> Issue Type: Bug
>Reporter: Sergey Antonov
>Assignee: Sergey Antonov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the log we see the following behavior:
> {noformat}
> 2019-07-04 06:29:03.649[WARN
> ][sys-#328%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#328%NODE%xyzGridNodeName% for timeout(ms)=16335
> 2019-07-04 06:29:03.649[WARN
> ][sys-#326%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#326%NODE%xyzGridNodeName% for timeout(ms)=13438
> 2019-07-04 06:29:03.649[WARN
> ][sys-#277%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#277%NODE%xyzGridNodeName% for timeout(ms)=11609
> 2019-07-04 06:29:03.649[WARN
> ][sys-#331%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#331%NODE%xyzGridNodeName% for timeout(ms)=18009
> 2019-07-04 06:29:03.649[WARN
> ][sys-#321%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#321%NODE%xyzGridNodeName% for timeout(ms)=15557
> 2019-07-04 06:29:03.650[WARN
> ][sys-#307%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#307%NODE%xyzGridNodeName% for timeout(ms)=27938
> 2019-07-04 06:29:03.649[WARN
> ][sys-#316%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#316%NODE%xyzGridNodeName% for timeout(ms)=12189
> 2019-07-04 06:29:03.649[WARN
> ][sys-#311%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#311%NODE%xyzGridNodeName% for timeout(ms)=11056
> 2019-07-04 06:29:03.650[WARN
> ][sys-#295%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#295%NODE%xyzGridNodeName% for timeout(ms)=20848
> 2019-07-04 06:29:03.649[WARN
> ][sys-#290%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#290%NODE%xyzGridNodeName% for timeout(ms)=14816
> 2019-07-04 06:29:03.649[WARN
> ][sys-#332%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#332%NODE%xyzGridNodeName% for timeout(ms)=14110
> 2019-07-04 06:29:03.649[WARN
> ][sys-#298%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#298%NODE%xyzGridNodeName% for timeout(ms)=10028
> 2019-07-04 06:29:03.650[WARN
> ][sys-#304%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#304%NODE%xyzGridNodeName% for timeout(ms)=19855
> 2019-07-04 06:29:03.650[WARN
> ][sys-#331%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#331%NODE%xyzGridNodeName% for timeout(ms)=41277
> 2019-07-04 06:29:03.650[WARN
> ][sys-#291%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#291%NODE%xyzGridNodeName% for timeout(ms)=17151
> 2019-07-04 06:29:03.650[WARN
> ][sys-#308%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#308%NODE%xyzGridNodeName% for timeout(ms)=39312
> 2019-07-04 06:29:03.650[WARN
> ][sys-#322%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#322%NODE%xyzGridNodeName% for timeout(ms)=43341
> 2019-07-04 06:29:03.650[WARN
> ][sys-#306%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#306%NODE%xyzGridNodeName% for timeout(ms)=21890
> 2019-07-04 06:29:03.650[WARN
> ][sys-#315%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#315%NODE%xyzGridNodeName% for timeout(ms)=18909
> 2019-07-04 06:29:03.650[WARN
> ][sys-#321%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#321%NODE%xyzGridNodeName% for timeout(ms)=74129
> 2019-07-04 06:29:03.650[WARN
> ][sys-#305%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#305%NODE%xyzGridNodeName% for timeout(ms)=26608
> 2019-07-04 06:29:03.650[WARN
> ][sys-#309%NODE%xyzGridNodeName%][o.a.i.i.p.c.p.pagemem.PageMemoryImpl]
> Parking thread=sys-#309%NODE%xyzGridNodeName% for timeout(ms)=77835
[jira] [Created] (IGNITE-12010) [TC Bot] Consider newly contributed test as blocker if it runs more that 1 minute.
Dmitriy Pavlov created IGNITE-12010: --- Summary: [TC Bot] Consider newly contributed test as blocker if it runs more that 1 minute. Key: IGNITE-12010 URL: https://issues.apache.org/jira/browse/IGNITE-12010 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Long-running tests should be scaled by the scale factor, and/or moved to Run All nightly -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (IGNITE-12004) CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields is flaky
[
https://issues.apache.org/jira/browse/IGNITE-12004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891791#comment-16891791
]
Ivan Pavlukhin commented on IGNITE-12004:
-
SQL {{UPDATE}} trims precision more than milliseconds for {{LocalTime}}.
Created a ticket for investigation IGNITE-12009.
Was reproduced only for Java 9+ because of increased precision of system clock.
Employed nanosecond precision in tests explicitly. Ignored a test for UPDATE
with nanos precision and added a test for UPDATE with millis precision instead.
> CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields is flaky
> --
>
> Key: IGNITE-12004
> URL: https://issues.apache.org/jira/browse/IGNITE-12004
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Affects Versions: 2.7.5
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> CacheQueryEntityWithDateTimeApiFieldsTest.testUpdateAllFields fails often
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-4227647830422954979=testDetails
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (IGNITE-12007) Latest "apacheignite/web-console-backend" docker image is broken
[
https://issues.apache.org/jira/browse/IGNITE-12007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16891744#comment-16891744
]
Evgenii Zhuravlev commented on IGNITE-12007:
[~dpavlov] that's not the reason to close the ticket. This is the real issue
and I see that users are facing it:
https://stackoverflow.com/questions/57179602/starting-webagent-on-apache-ignite-for-docker
> Latest "apacheignite/web-console-backend" docker image is broken
>
>
> Key: IGNITE-12007
> URL: https://issues.apache.org/jira/browse/IGNITE-12007
> Project: Ignite
> Issue Type: Bug
> Components: UI
>Affects Versions: 2.7
>Reporter: Igor Belyakov
>Priority: Critical
>
> It's not possible to run docker container by using the latest version of
> "apacheignite/web-console-backend" image.
> Next error happens on the start:
> {code:java}
> npm ERR! A complete log of this run can be found in:
> npm ERR! /root/.npm/_logs/2019-07-23T14_24_40_353Z-debug.log
> npm ERR! path /opt/web-console/package.json
> npm ERR! code ENOENT
> npm ERR! errno -2
> npm ERR! syscall open
> npm ERR! enoent ENOENT: no such file or directory, open
> '/opt/web-console/package.json'
> npm ERR! enoent This is related to npm not being able to find a file.
> npm ERR! enoent{code}
> How to reproduce:
> Run container by using docker-compose as described here:
> [https://hub.docker.com/r/apacheignite/web-console-backend]
>
> Seems like it was broken by the next commit:
> [https://github.com/apache/ignite/commit/4c295f8f468ddfce458948c17c13b1748b13e918#diff-ec0d595d738c4207e08ce210624e902aR22]
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (IGNITE-12009) Clarify java.time.LocalTime mapping in SQL queries
Ivan Pavlukhin created IGNITE-12009:
---
Summary: Clarify java.time.LocalTime mapping in SQL queries
Key: IGNITE-12009
URL: https://issues.apache.org/jira/browse/IGNITE-12009
Project: Ignite
Issue Type: Task
Components: sql
Affects Versions: 2.7.5
Reporter: Ivan Pavlukhin
Currently mappings between, java.time. java.sql and h2 temporal types provokes
some surprising behavior. Need to figure out if there are bugs or it is an
expected behavior.
One example is using java.time.LocalTime as QueryEntity field. If a value of
such column is modified by SQL {{UPDATE}} then precision more than milliseconds
is lost.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (IGNITE-11961) Provide JMX metrics for PME timings
[ https://issues.apache.org/jira/browse/IGNITE-11961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amelchev Nikita updated IGNITE-11961: - Description: Currently, partition map exchange timings printed to log(IGNITE-10493). It will be useful if we allow external tools to collect and aggregate partition map exchange metrics. UPD: Need to implement next metrics: - сacheOperationsBlockedDuration (long) - totalCacheOperationsBlockedDuration (long) was:Currently, partition map exchange timings printed to log(IGNITE-10493). It will be useful if we allow external tools to collect and aggregate partition map exchange metrics. > Provide JMX metrics for PME timings > --- > > Key: IGNITE-11961 > URL: https://issues.apache.org/jira/browse/IGNITE-11961 > Project: Ignite > Issue Type: Improvement >Reporter: Amelchev Nikita >Assignee: Amelchev Nikita >Priority: Major > Fix For: 2.8 > > > Currently, partition map exchange timings printed to log(IGNITE-10493). It > will be useful if we allow external tools to collect and aggregate partition > map exchange metrics. > UPD: Need to implement next metrics: > - сacheOperationsBlockedDuration (long) > - totalCacheOperationsBlockedDuration (long) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-11410) Sandbox for user-defined code
[ https://issues.apache.org/jira/browse/IGNITE-11410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus updated IGNITE-11410: - Summary: Sandbox for user-defined code (was: Restricted environment in which to run user-defined code securely) > Sandbox for user-defined code > - > > Key: IGNITE-11410 > URL: https://issues.apache.org/jira/browse/IGNITE-11410 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Denis Garus >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > We should provide a restricted environment in which to run user-defined code > securely. To get it done, we would use the java sandbox model. > The java sandbox model allows restricting access from user-defined code to > the system resources or security-sensitive feature of java, for example, > reflection. > The user-defined code contains: > - StreamReceiver for DataStreamer: > - EntryProcessor; > - ComputeJob; > - filter and transformer for ScanQuery. > The user-defined code will get permissions from GridSecuerityProcessor > (security plugin). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-11410) Sandbox for user-defined code
[ https://issues.apache.org/jira/browse/IGNITE-11410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus updated IGNITE-11410: - Description: We should provide a restricted environment (sandbox) in which to run user-defined code securely. To get it done, we would use the java sandbox model. The java sandbox model allows restricting access from user-defined code to the system resources or security-sensitive feature of java, for example, reflection. The user-defined code contains: - StreamReceiver for DataStreamer: - EntryProcessor; - ComputeJob; - filter and transformer for ScanQuery. The user-defined code will get permissions from GridSecuerityProcessor (security plugin). was: We should provide a restricted environment in which to run user-defined code securely. To get it done, we would use the java sandbox model. The java sandbox model allows restricting access from user-defined code to the system resources or security-sensitive feature of java, for example, reflection. The user-defined code contains: - StreamReceiver for DataStreamer: - EntryProcessor; - ComputeJob; - filter and transformer for ScanQuery. The user-defined code will get permissions from GridSecuerityProcessor (security plugin). > Sandbox for user-defined code > - > > Key: IGNITE-11410 > URL: https://issues.apache.org/jira/browse/IGNITE-11410 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Denis Garus >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > We should provide a restricted environment (sandbox) in which to run > user-defined code securely. To get it done, we would use the java sandbox > model. > The java sandbox model allows restricting access from user-defined code to > the system resources or security-sensitive feature of java, for example, > reflection. > The user-defined code contains: > - StreamReceiver for DataStreamer: > - EntryProcessor; > - ComputeJob; > - filter and transformer for ScanQuery. > The user-defined code will get permissions from GridSecuerityProcessor > (security plugin). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (IGNITE-11410) Restricted environment in which to run user-defined code securely
[ https://issues.apache.org/jira/browse/IGNITE-11410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Garus updated IGNITE-11410: - Summary: Restricted environment in which to run user-defined code securely (was: Providing a restricted environment in which to run user-defined code securely) > Restricted environment in which to run user-defined code securely > - > > Key: IGNITE-11410 > URL: https://issues.apache.org/jira/browse/IGNITE-11410 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Denis Garus >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > We should provide a restricted environment in which to run user-defined code > securely. To get it done, we would use the java sandbox model. > The java sandbox model allows restricting access from user-defined code to > the system resources or security-sensitive feature of java, for example, > reflection. > The user-defined code contains: > - StreamReceiver for DataStreamer: > - EntryProcessor; > - ComputeJob; > - filter and transformer for ScanQuery. > The user-defined code will get permissions from GridSecuerityProcessor > (security plugin). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
