Alexey Kuznetsov created IGNITE-13303:
-
Summary: Update mockito from 1.10.19 to 3.x
Key: IGNITE-13303
URL: https://issues.apache.org/jira/browse/IGNITE-13303
Project: Ignite
Issue Type
Alex, Denis
Issue with moving of Web Console to separate repository is merged to master.
See: https://issues.apache.org/jira/browse/IGNITE-13038
Please, consider to cherry-pick to ignite-2.9
---
Alexey Kuznetsov
you tried "real" repository address
> https://gitbox.apache.org/repos/asf/ignite-web-console.git ?
>
> 2020-07-17 14:01 GMT+03:00, Alexey Kuznetsov :
> > Dmitriy,
> >
> > I'm working on moving Web Console to separate repository IGNITE-13038
> > <h
Dmitriy,
I'm working on moving Web Console to separate repository IGNITE-13038
<https://issues.apache.org/jira/browse/IGNITE-13038>,
but I can not commit to https://github.com/apache/ignite-web-console
Do you know how I can be granted with commit rights?
---
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-13262:
-
Summary: Remove GridClientUtils#shutdownNow() as full duplicate of
U#shutdownNow
Key: IGNITE-13262
URL: https://issues.apache.org/jira/browse/IGNITE-13262
Alex,
Can you cherry-pick to Ignite 2.9 this issue:
https://issues.apache.org/jira/browse/IGNITE-13246 ?
This issue is about BASELINE events and it is very useful for notification
external tools about changes in baseline.
Thank you!
---
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-13105:
-
Summary: Spring data 2.0
IgniteRepositoryQuery#transformQueryCursor contains cursor leak
Key: IGNITE-13105
URL: https://issues.apache.org/jira/browse/IGNITE-13105
Alexey Kuznetsov created IGNITE-13104:
-
Summary: Spring data 2.0 IgniteRepositoryImpl#deleteAllById
contains wrong code
Key: IGNITE-13104
URL: https://issues.apache.org/jira/browse/IGNITE-13104
-1 Prohibit
>From my point of view, we should not deprecate the old API if the new API
is marked as experemental.
On Mon, Feb 10, 2020 at 4:47 PM Konstantin Orlov
wrote:
> -1 Prohibit
>
> We should not deprecate the old API if the new API could change in the
> near future.
a Kasnacheev demonstrated [4], the more 3rd party
> >> libraries
> >>> we
> >>>>>> have, the more potential vulnerabilities will show up in audit
> >> tools.
> >>>>> This
> >>>>>> may be a formal barrier for Apache Ignite adoption and moving to
> >>>>> production
> >>>>>> for many users. Having a slim image with the minimum number of
> >>>>> dependencies
> >>>>>> (yet complete enough to fit the majority of use-cases)
> >> significantly
> >>>>>> reduces this risk.
> >>>>>>
> >>>>>> I wonder what community thinks regarding this idea? Given the
> >> recent
> >>>>> study
> >>>>>> of Apache Ignite use-cases, I suggest the following list of modules
> >>> to
> >>>> be
> >>>>>> included to the slim release/image (a subject to discuss, of
> >> course):
> >>>>>> * ignite-core
> >>>>>> * ignite-indexing
> >>>>>> * ignite-rest-http
> >>>>>> * ignite-spring
> >>>>>> * ignite-log4j
> >>>>>> * ignite-log4j2
> >>>>>> * ignite-slf4j
> >>>>>> * ignite-urideploy
> >>>>>> * ignite-kubernetes
> >>>>>> * ignite-opencensus
> >>>>>>
> >>>>>> [1]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Ignite-3-0-and-to-be-removed-list-td42330.html
> >>>>>> [2]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12358-Migrate-ZeroMQ-module-to-ignite-extensions-td45067.html
> >>>>>> [3]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-12361-Migrate-Flume-module-to-ignite-extensions-td45010.html
> >>>>>> [4]
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> http://apache-ignite-developers.2346864.n4.nabble.com/Apache-Ignite-2-8-RELEASE-Time-Scope-Manager-td43616i100.html#a44994
> >>>>>>
> >>>>>> --AG
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>
--
Alexey Kuznetsov
ember 23, 2019, sgtech19 wrote:
> >>>>
> >>>>> Hello team,
> >>>>> I would like to add a new feature to the existing
> >>> visor
> >>>>> commands. Could you give me some direction on how to achieve this if
> >>> its
> >>>>> possible? Do we need a visor plugin ? if so,please provide any
> >> example
> >>> of
> >>>>> this plugin .
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> -
> >>>> Denis
> >>>
> >>>
> >>>
> >>> --
> >>> Best regards,
> >>> Ivan Pavlukhin
> >>>
> >>
>
>
--
Alexey Kuznetsov
>
> > I tend to agree with Alexey - API compatibility should be preserved
> within
> > a major version. I would oppose doing such a change in 2.x.
> >
> > If this is planned for 3.0, then it's a definite +1 from me.
> >
> > -Val
> >
> > On Wed, D
es
> > > towards this. If I won't see any activity, I will go forward with JIRA
> > > issue.
> > >
> > > Previous discussion: https://issues.apache.org/jira/browse/IGNITE-5565
> > > We tried to move it to Quartz but it changed semantics in some ways.
> > >
> > > Regards,
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>
--
Alexey Kuznetsov
or external systems and only useful thing is self
> documentation.
>
> On Wed, Nov 6, 2019 at 12:42 PM Nikolay Izhikov
> wrote:
> >
> > Hello, Alexey.
> >
> > I'm +1.
> > Let's do it.
> >
> > В Ср, 06/11/2019 в 16:37 +0700, Alexey
dules/core/src/main/java/org/apache/ignite/spi/metric/Metric.java
--
Alexey Kuznetsov
heIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum
> > >
> > > The vote is formal, see voting guidelines
> > > https://www.apache.org/foundation/voting.html
> > >
> > > +1 - to accept Apache Ignite 2.7.6-rc2
> > > 0 - don't care either way
> > > -1 - DO NOT accept Apache Ignite Ignite 2.7.6-rc2 (explain why)
> > >
> > > See notes on how to verify release here
> > > https://www.apache.org/info/verification.html
> > > and
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-ReleaseVerification
> > >
> > > This vote will be open for at least 72 hours till September 16, 09:00
> > UTC.
> > >
> > >
> >
> https://www.timeanddate.com/countdown/to?year=2019&month=9&day=16&hour=09&min=0&sec=0&p0=utc-1
> > >
> > > -- Alexey Goncharuk
> > >
> >
>
--
Alexey Kuznetsov
;> > * Fixed a bug that made it impossible to change the
> > inline_size
> > > > > >> property
> > > > > >> >of an existing index after it was dropped and recreated with a
> > > > different
> > > > > >> >value
> > > > > >> >
> > > > > >> >RELEASE NOTES:
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob;f=RELEASE_NOTES.txt;hb=ignite-2.7.6
> > > > > >> >
> > > > > >> >Complete list of closed issues:
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.7.6
> > > > > >> >
> > > > > >> >DEVNOTES
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.7.6
> > > > > >> >
> > > > > >> >The vote is formal, see voting guidelines
> > > > > >> >https://www.apache.org/foundation/voting.html
> > > > > >> >
> > > > > >> >+1 - to accept Apache Ignite 2.7.6-rc1
> > > > > >> >0 - don't care either way
> > > > > >> >-1 - DO NOT accept Apache Ignite Ignite 2.7.6-rc1 (explain why)
> > > > > >> >
> > > > > >> >See notes on how to verify release here
> > > > > >> >https://www.apache.org/info/verification.html
> > > > > >> >and
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> > > > > >> >
> > > > > >> >This vote will be open for at least 3 days till Sun Aug 25,
> 18:00
> > > > UTC.
> > > > > >> >
> > > > > >>
> > > >
> > >
> >
> https://www.timeanddate.com/countdown/to?year=2019&month=8&day=25&hour=18&min=0&sec=0&p0=utc-1
> > > > > >> >
> > > > > >> >Best Regards,
> > > > > >> >Dmitriy Pavlov
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> Zhenya Stanilovsky
> > > > > >>
> > > > > >
> > > >
> > >
> >
> >
> > --
> >
> > Best regards,
> > Alexei Scherbakov
> >
>
--
Alexey Kuznetsov
:
> > > >
> > > > Hi,
> > > >
> > > > I have raised a PR for the below issue.
> > > >
> > > > IGNITE-7285 Add default query timeout
> > > >
> > > > PR - https://github.com/apache/ignite/pull/6490
> > > >
> > > > Please take a look and share feedback.
> > > >
> > > > Regards,
> > > > Saikat
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-11752:
-
Summary: Refactor usages of "System.getenv(key)" to
IgniteSystemProperties.getString(key)
Key: IGNITE-11752
URL: https://issues.apache.org/jira/browse/IG
gt;
> > Hello!
> >
> > I think it does indeed makes sense to always use
> > *IgniteSystemProperties.getStri**ng*
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 11 апр. 2019 г. в 16:40, Alexey Kuznetsov :
> >
>
in tests, because it easily to set system
property in Java code,
and very non trivial to do the same for environment variables.
Does any body have objections if I create JIRA issue (with pull request) to
replace all direct calls of "System.getenv(key)" with
IgniteSystemProperti
Alexey Kuznetsov created IGNITE-11710:
-
Summary: Web Console: Expose callback to ui-grid.api for
manipulations with ui-grid.
Key: IGNITE-11710
URL: https://issues.apache.org/jira/browse/IGNITE-11710
Alexey Kuznetsov created IGNITE-11506:
-
Summary: Web Console: Adjust CSS styles to correctly show "User
name" in top menu.
Key: IGNITE-11506
URL: https://issues.apache.org/jira/browse/IG
Alexey Kuznetsov created IGNITE-11360:
-
Summary: Web Console: Should detect situation when session on
backed expired / removed
Key: IGNITE-11360
URL: https://issues.apache.org/jira/browse/IGNITE-11360
Alexey Kuznetsov created IGNITE-11338:
-
Summary: Web Console: Current cache "jump" after edit on "Basic
configuration" screen
Key: IGNITE-11338
URL: https://issues.apache.org/jira
Alexey Kuznetsov created IGNITE-11285:
-
Summary: Conflicting javadocs for PagesFillFactor
Key: IGNITE-11285
URL: https://issues.apache.org/jira/browse/IGNITE-11285
Project: Ignite
Issue
Hi,
I think it make sense to remove Windows version detection, because Java 8+
will simply not even start on old Windows.
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-11224:
-
Summary: Cleanup IgniteUtils from checks for old OS-es that not
supported by Java 8+
Key: IGNITE-11224
URL: https://issues.apache.org/jira/browse/IGNITE-11224
Alexey Kuznetsov created IGNITE-11166:
-
Summary: Web Agent: Host name verifier should be disabled in case
of "-Dtrust.all=true".
Key: IGNITE-11166
URL: https://issues.apache.org/jira/browse/IG
k, we should rework control.sh utility in Apache Ignite 3.0
> > > release.
> > > > I made umbrella ticket [1] for it.
> > > >
> > > > For a start we should move utitlity from ignite-core to separate
> module
> > > > [2]. It's enable using
Alexey Kuznetsov created IGNITE-10994:
-
Summary: NPE GridPartitionedSingleGetFuture after activation
Key: IGNITE-10994
URL: https://issues.apache.org/jira/browse/IGNITE-10994
Project: Ignite
Alexey Kuznetsov created IGNITE-10936:
-
Summary: Web Console: Add support for single select mode on
ui-grid.
Key: IGNITE-10936
URL: https://issues.apache.org/jira/browse/IGNITE-10936
Project
Alexey Kuznetsov created IGNITE-10923:
-
Summary: Minor cleanup
Key: IGNITE-10923
URL: https://issues.apache.org/jira/browse/IGNITE-10923
Project: Ignite
Issue Type: Bug
Alexey Kuznetsov created IGNITE-10916:
-
Summary: Add guard for cache restarting in progress for Visor
tasks.
Key: IGNITE-10916
URL: https://issues.apache.org/jira/browse/IGNITE-10916
Project
Alexey Kuznetsov created IGNITE-10914:
-
Summary: Web Console: Account email should be unique
Key: IGNITE-10914
URL: https://issues.apache.org/jira/browse/IGNITE-10914
Project: Ignite
Alexey Kuznetsov created IGNITE-10889:
-
Summary: Web Console should work with Web Agent started from
Docker image.
Key: IGNITE-10889
URL: https://issues.apache.org/jira/browse/IGNITE-10889
I'm using comm...@ignite.apache.org to track who and what commits to
master :)
--
Alexey Kuznetsov
.11. Originally we have the old version of Scala
> for supporting old versions of Apache Spark.
>
> But support for Scala 2.10 was removed as of 2.3.0 Apache Spark released.
> And current version if 2.4.0.
>
> Please share your opinion
>
> Best regards,
> Yuriy Babak
>
--
Alexey Kuznetsov
t; > > it.
> >> > >> > > > > > > > > > > > > > > > > > Others won't notice it, because
> it
> >> will
> >> > >> get
> >> > >> > > > lost
> >> >
Alexey Kuznetsov created IGNITE-10875:
-
Summary: Web Console: Update tooltip
Key: IGNITE-10875
URL: https://issues.apache.org/jira/browse/IGNITE-10875
Project: Ignite
Issue Type
Yuriy,
I think, for the sake of code simplicity we can track all queries.
in other case we will need to parse SQL text and detect that current query
is the EXPLAIN one.
--
Alexey Kuznetsov
rameters? I know -D or - X but can't recall what -J is supposed to be
> used for.
>
> --
> Denis
>
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-10839:
-
Summary: Web Console: Email confirmation
Key: IGNITE-10839
URL: https://issues.apache.org/jira/browse/IGNITE-10839
Project: Ignite
Issue Type
Alexey Kuznetsov created IGNITE-10833:
-
Summary: Web Console: Implement query cancel
Key: IGNITE-10833
URL: https://issues.apache.org/jira/browse/IGNITE-10833
Project: Ignite
Issue Type
:
> > > > > >
> > > > > > > Yakov,
> > > > > > >
> > > > > > > No, the mentioned discussion didn’t turn into a JIRA ticket.
> > > > > > >
> > > > > > > Alex K., please follow to some thoughts from there and wrap
> them
> > up
> > > > in
> > > > > a
> > > > > > > form of the ticket.
> > > > > > >
> > > > > > > —
> > > > > > > Denis
> > > > > > >
> > > > > > > > On Jun 26, 2017, at 2:58 AM, Yakov Zhdanov <
> > yzhda...@apache.org>
> > > > > > wrote:
> > > > > > > >
> > > > > > > > Guys, I remember we discussed this some time ago.
> > > > > > > >
> > > > > > > >
> > > > > > > http://apache-ignite-developers.2346864.n4.nabble.
> > > > > > com/Tasks-Scheduling-and-Chaining-td14293.html
> > > > > > > >
> > > > > > > > Denis, do you have any ticket or SoW?
> > > > > > > >
> > > > > > > > --Yakov
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
Alexey Kuznetsov
"reduce" queries? Or only final "map" ones?
--
Alexey Kuznetsov
Hi,
>From my experience it is better when all needed stuff available on GitHub.
It is very comfortable when thinks like, "read me", "change log", "how to
build", "how to contribute" and so on available on GitHub.
No need to open some external links.
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-10668:
-
Summary: Web Console: Prepare sample NGINX config with SSL and
ciphers support
Key: IGNITE-10668
URL: https://issues.apache.org/jira/browse/IGNITE-10668
Alexey Kuznetsov created IGNITE-10661:
-
Summary: Web Console: E2E tests failed because of problems with
Docker file
Key: IGNITE-10661
URL: https://issues.apache.org/jira/browse/IGNITE-10661
Alexey Kuznetsov created IGNITE-10611:
-
Summary: Web Console: Refactor ActivitiesService to use uer object
instead of id.
Key: IGNITE-10611
URL: https://issues.apache.org/jira/browse/IGNITE-10611
Vyacheslav,
Thanks for detailed explanation.
As far as I see, we CAN support services on deactivated cluster, but it
does not seems a good idea from end user perspective.
I'm thinking that in my case (sending telemetry from cluster) I will go
another way.
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-10610:
-
Summary: Change error to warning in VisorMultiNodeTask when no
mapped jobs found.
Key: IGNITE-10610
URL: https://issues.apache.org/jira/browse/IGNITE-10610
Alexey Kuznetsov created IGNITE-10609:
-
Summary: Failed to remove cache from service configuration.
Key: IGNITE-10609
URL: https://issues.apache.org/jira/browse/IGNITE-10609
Project: Ignite
are allowed, right)?
>
> 2. That should be covered in the existing EIP
>
> --
> Denis
>
> On Fri, Dec 7, 2018 at 6:20 AM Alexey Kuznetsov
> wrote:
>
> > Igniters,
> >
> > I would like to discuss how we can support following features for
> Servi
have also add some flag on service configuration?
And store such services the same way as we store user information for
authentication in metastorage?
What do yo think?
I can create issues in JIRA if we agreed to support them.
--
Alexey Kuznetsov
this, I need that services should:
1) Work when cluster NOT ACTIVE.
2) Auto restart with cluster (when cluster was restarted).
Could we support mentioned features on "Service Grid redesign - phase 2" ?
Please let me know.
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-10564:
-
Summary: Create task to collect rebalance metrics
Key: IGNITE-10564
URL: https://issues.apache.org/jira/browse/IGNITE-10564
Project: Ignite
Issue
Alexey Kuznetsov created IGNITE-10552:
-
Summary: Web Agent: Improve logging when cluster topology changed
Key: IGNITE-10552
URL: https://issues.apache.org/jira/browse/IGNITE-10552
Project: Ignite
Alexey Kuznetsov created IGNITE-10533:
-
Summary: Web Console: Images outdated on web site.
Key: IGNITE-10533
URL: https://issues.apache.org/jira/browse/IGNITE-10533
Project: Ignite
Issue
Alexey Kuznetsov created IGNITE-10525:
-
Summary: Web Console: "Import models" dialog should be a singleton.
Key: IGNITE-10525
URL: https://issues.apache.org/jira/browse/IGNITE-10525
o public
> API
> > (to IgniteConfiguration for example).
> >
> > Also maybe we should change cache metrics distributing strategy? For
> > example, collect metrics by request via communication SPI or subscribe
> to a
> > limited set of cache/metrics, etc.
> >
> > Thoughts?
> >
> > [1]: https://issues.apache.org/jira/browse/IGNITE-10172
> >
>
--
Alexey Kuznetsov
syn
> - Dmitriy Pavlov
> - Nikolay Izhikov
>
> Vote thread:
>
>
> http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-7-0-RC2-td38788.html
>
--
Alexey Kuznetsov
+1 (binding)
1. Download sources: *OK*
2. Build ignite from sources: *OK*
3. Build Web Console from sources: *OK*
4. Build Web Agent from sources: *OK*
5. Start node, Web agent and Web Console: *OK*
6. Executed several SQL queries from Web Console: *OK*
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-10490:
-
Summary: Web Console: ui-grid should refresh its content on parent
element resize
Key: IGNITE-10490
URL: https://issues.apache.org/jira/browse/IGNITE-10490
Alexey Kuznetsov created IGNITE-10433:
-
Summary: Web Console: "Import models" dialog doesn't unsubscribe
from watching agent after closing
Key: IGNITE-10433
URL: https://issues.apache.org/jir
Hi,
We found a regression https://issues.apache.org/jira/browse/IGNITE-10432
Please take a look.
--
Alexey Kuznetsov
nite-developers.2346864.n4.nabble.com/Time-to-remove-automated-messages-from-the-devlist-td37484i20.html
>
--
Alexey Kuznetsov
(cfg1, ... cfgN);
> > > > > >
> > > > > > where cfgX is a new cache configuration, which contains the name
> of
> > > an
> > > > > > existing persistent cache.
> > > > > >
> > > > > > The obvious limitation:
> > > > > > - affinity key mapping couldn't be changed;
> > > > > > - count of partitions couldn't be changed;
> > > > > > - MVCC couldn't be turned off/on;
> > > > > > - persistent couldn't be turned off;
> > > > > > - group settings couldn't be changed (group name);
> > > > > > - if cache belongs to group it's needed to restart all of them.
> > > > > >
> > > > > > Failure scenario is the crucial thing (and most difficult):
> > > > > > - initiator fail;
> > > > > > - cluster restart at any stage;
> > > > > > - joining/starting offline nodes.
> > > > > >
> > > > > > Some thoughts about implementation:
> > > > > > - stop cache with destroy=false;
> > > > > > - start cache dynamically with new configuration;
> > > > > > - if indexes settings changed - remove index.bin to start
> > indexation;
> > > > > > - change blt-history when start cache initiated to not allow join
> > > nodes
> > > > > > with old configuration;
> > > > > > - use restartId (IGNITE-8911) to not allow to start cache in
> > between.
> > > > > >
> > > > > > Your thoughts? Would it be a useful feature?
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Eduard.
> > > >
> > >
> >
>
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-10351:
-
Summary: Web Console: add new fields of IgniteConfiguration
(sysWorkerBlockedTimeout and checkpointReadLockTimeout) to UI configurator
Key: IGNITE-10351
URL: https
Alexey Kuznetsov created IGNITE-10349:
-
Summary: Web Console: Add check for supported MongoDb version
before WC start
Key: IGNITE-10349
URL: https://issues.apache.org/jira/browse/IGNITE-10349
Alexey Kuznetsov created IGNITE-10320:
-
Summary: Web Console: Memory leak in char component
Key: IGNITE-10320
URL: https://issues.apache.org/jira/browse/IGNITE-10320
Project: Ignite
Alexey Kuznetsov created IGNITE-10293:
-
Summary: VisorNodeDataCollectorJob should not collect caches info
on inactive cluster
Key: IGNITE-10293
URL: https://issues.apache.org/jira/browse/IGNITE-10293
Alexey Kuznetsov created IGNITE-10245:
-
Summary: o.a.i.internal.util.nio.ssl.GridNioSslFilter failed with
Assertion if invalid SSL Cipher suite name specified
Key: IGNITE-10245
URL: https://issues.apache.org
Hi!
I have filter for e-mail from JIRA (very useful, I can quick search issue
there without visiting JIRA).
And I'm just deleting tons of e-mails from GitBox & about PRs.
I don't know what for we need them?
May by we try to move GitBox & PRs-related mails first and see how it
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
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
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
Alexey Kuznetsov created IGNITE-10083:
-
Summary: Web Console: Create emulator of large cluster for test
purposes
Key: IGNITE-10083
URL: https://issues.apache.org/jira/browse/IGNITE-10083
Project
Alexey Kuznetsov created IGNITE-10081:
-
Summary: Web Console: Add support for timeout on Promises that
executed against Web Agent
Key: IGNITE-10081
URL: https://issues.apache.org/jira/browse/IGNITE-10081
Alexey Kuznetsov created IGNITE-10076:
-
Summary: Web Console: Investigate big number parsing in JSON
Key: IGNITE-10076
URL: https://issues.apache.org/jira/browse/IGNITE-10076
Project: Ignite
Alexey Kuznetsov created IGNITE-10032:
-
Summary: Web Agent: Optimize collecting topology from cluster
Key: IGNITE-10032
URL: https://issues.apache.org/jira/browse/IGNITE-10032
Project: Ignite
Alexey Kuznetsov created IGNITE-10031:
-
Summary: REST: Introduce "caches" param for "top" command.
Key: IGNITE-10031
URL: https://issues.apache.org/jira/browse/IGNITE-10031
Alexey Kuznetsov created IGNITE-10016:
-
Summary: Web Console: ClusterLoginService should return
credentials modal as singelton
Key: IGNITE-10016
URL: https://issues.apache.org/jira/browse/IGNITE-10016
Alexey Kuznetsov created IGNITE-9941:
Summary: Web Console: Add option to disable self-registration on
Web Console
Key: IGNITE-9941
URL: https://issues.apache.org/jira/browse/IGNITE-9941
Project
Alexey Kuznetsov created IGNITE-9938:
Summary: Update ScalaTest from 2.2.4 to 2.2.6
Key: IGNITE-9938
URL: https://issues.apache.org/jira/browse/IGNITE-9938
Project: Ignite
Issue Type
stop using them for multi-word names,
> 3. and make them not mandatory at all (what it is actually already true,
> because of no any mention in the main code-style article).
>
>
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-9887:
Summary: A lot of exceptions on cluster deactivation.
Key: IGNITE-9887
URL: https://issues.apache.org/jira/browse/IGNITE-9887
Project: Ignite
Issue
Alexey Kuznetsov created IGNITE-9863:
Summary: Refactor VisorDataTransferObject to common class
Key: IGNITE-9863
URL: https://issues.apache.org/jira/browse/IGNITE-9863
Project: Ignite
Alexey Kuznetsov created IGNITE-9862:
Summary: Web Console: Add support for "date", "time" and
"date-and-time" on InputDialog
Key: IGNITE-9862
URL: https://issues.apac
Alexey Kuznetsov created IGNITE-9839:
Summary: Web Console: Migrate to new API of RxJS
Key: IGNITE-9839
URL: https://issues.apache.org/jira/browse/IGNITE-9839
Project: Ignite
Issue Type
Alexey Kuznetsov created IGNITE-9811:
Summary: Web Console: Do not block "Save" button in case some
inputs are invalid
Key: IGNITE-9811
URL: https://issues.apache.org/jira/browse/I
Alexey Kuznetsov created IGNITE-9809:
Summary: Web Console: Minor Fixes
Key: IGNITE-9809
URL: https://issues.apache.org/jira/browse/IGNITE-9809
Project: Ignite
Issue Type: Task
Alexey Kuznetsov created IGNITE-9808:
Summary: Web Console: Refactor sockets caching
Key: IGNITE-9808
URL: https://issues.apache.org/jira/browse/IGNITE-9808
Project: Ignite
Issue Type
Alexey Kuznetsov created IGNITE-9807:
Summary: Web Agent: Add support for cluster ID
Key: IGNITE-9807
URL: https://issues.apache.org/jira/browse/IGNITE-9807
Project: Ignite
Issue Type
Alexey Kuznetsov created IGNITE-9795:
Summary: Web Agent: Improve information message in case REST
command failed on cluster
Key: IGNITE-9795
URL: https://issues.apache.org/jira/browse/IGNITE-9795
ul if MBeans are not allowed e.g. for
security reasons.*"
The fix is trivial (one liner + simple text).
I can contribute the fix for this bug.
1. https://issues.apache.org/jira/browse/IGNITE-9792
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-9792:
Summary: Setting system property IGNITE_MBEANS_DISABLED to true
lead to NPE.
Key: IGNITE-9792
URL: https://issues.apache.org/jira/browse/IGNITE-9792
Project
Alexey Kuznetsov created IGNITE-9733:
Summary: Web Console: Add support for "type=number" on InputDialog
Key: IGNITE-9733
URL: https://issues.apache.org/jira/browse/IGNITE-9733
Proje
Vova,
Huge +1 to do a stabilization.
--
Alexey Kuznetsov
Alexey Kuznetsov created IGNITE-9662:
Summary: Web Console: Optimize Nginx settings
Key: IGNITE-9662
URL: https://issues.apache.org/jira/browse/IGNITE-9662
Project: Ignite
Issue Type
1 - 100 of 801 matches
Mail list logo