>
> Currently, the dictionary for decompression is only stored on heap. After
> restart there's compressed data in the PDS, but there's no dictionary :)
Basically, it means that I've lost my data, right? How about persisting
data to disk.
Overall, we need Vladimir Ozerov to check the contributio
Guys,
I believe we should preserve the behavior that we have now. What happens to
services if we restart a persistent cluster running 2.6? Are services
recreated or not? If YES, we should make sure the same happens after
redesign. Would be even better if we preserve compatibility, i.e. allow
seaml
Hi Ignite Users, Developers, and Enthusiasts,
It's natural to assume that a newcomer has little to offer the Apache
Ignite. However, you can be surprised at how much each newcomer can help,
even now.
I would propose to run a hackathon on the next Apache Ignite meetup. In
parallel with talks, an a
Not sure I understood what bot statistic reduction means.
As far as I understood, you also mean locating failure automatically with
re-runs on specific git revisions (hashes). I found it will be a good
contribution to TC Bot for both flaky and non-flaky failures detection. E.g
failure occurred aft
I hope Vyacheslav can comment better than me. I suppose it is, more or
less, rectifications and clarifications of design aspects. Not overall
redesign.
I also hope Igniters, especially Services experts, will join the discussion
in the separate topic. Now after a couple of days there is no reaction
IntelliJ Idea shows missing @Override annotation on my installation. Not
sure it comes from our inspection or not.
Anyway, count on me.
пт, 24 авг. 2018 г. в 9:25, Maxim Muzafarov :
> Folks,
>
> I think we can make a small step further with Ignite Inspections.
>
> I've created these tickets [1],
Hi Anton,
Do you have objections about a partial rollback of changes?
Sincerely,
Dmitriy Pavlov
пт, 24 авг. 2018 г. в 14:24, ARomantsov :
> Hello, Igniters.
>
> I'm testing some java keys with ignite.bat and notice that using more that
> four keys lead to internal problem and ignite.bat ignorin
On Fri, Aug 24, 2018 at 2:50 PM, Dmitriy Pavlov
wrote:
> Hi Dmitriy, I suppose it highly depends on how fast community will come to
> a consensus about design. So it is up to us to make this happen
>
I am confused then. If we are still discussing design, then we are miles
away. Do you know if th
Denis M. & Val please share your vision about this topic.
пт, 24 авг. 2018 г. в 15:52, Vyacheslav Daradur :
> Nick, Antron, thank you for stepping in.
>
> AFAIK, Ignite cluster can move its state to a new version of Ignite
> using persistence only.
>
> Since Ignite v.2.3 persistence is configured
Hi Dmitriy, I suppose it highly depends on how fast community will come to
a consensus about design. So it is up to us to make this happen
сб, 25 авг. 2018 г. в 0:05, Dmitriy Setrakyan :
> Nikolai,
>
> To my knowledge, some significant changes to the service grid
> implementation were going to ma
Hi Ilya,
Thank you for your efforts in fixing tests. I've merged this patch. Looking
forward to your new contributions.
I hope someday all test failures are fixed in such an operative manner.
Sincerely,
Dmitriy Pavlov
пт, 24 авг. 2018 г. в 19:41, Ilya Kasnacheev :
> https://issues.apache.org/j
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4617
---
Nikolai,
To my knowledge, some significant changes to the service grid
implementation were going to make it into 2.7. However, I am right now
seeing other threads about the service grid in which the new design is just
being discussed. This shows that service grid is not release ready.
Do you know
PR is fully ready.
I'm waiting final approve from Vladimir Ozerov.
Hope, This will be merged in master on Monday :).
В Пт, 24/08/2018 в 11:47 -0700, Pavel Petroshenko пишет:
> Hi Nikolay,
>
> Thank you for the heads up. The dependency should be resolved before the
> clients are merged to maste
Hi Nikolay,
Thank you for the heads up. The dependency should be resolved before the
clients are merged to master, so the sooner you merge the PR the better.
p.
On Fri, Aug 24, 2018 at 12:47 AM, Nikolay Izhikov
wrote:
> Hello, Pavel.
>
> Please, be aware of IGNITE-6055 [1]
>
> I'm edit thin pr
GitHub user Mmuzaf opened a pull request:
https://github.com/apache/ignite/pull/4618
IGNITE-9311: add override annotation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mmuzaf/ignite ignite-9311
Alternatively you can review and
Nikolay,
If there are multiple configuration in XML, IgniteContext will always use
only one of them. Looks like current approach simply doesn't work. I
propose to report schema name as 'database' in Spark. If there are multiple
clients, you would create multiple sessions and multiple catalogs.
Ma
Andrew Medvedev created IGNITE-9381:
---
Summary: p2p does not undeploy ScanQuery IgniteBiPredicate filter
on client node disconnect
Key: IGNITE-9381
URL: https://issues.apache.org/jira/browse/IGNITE-9381
https://issues.apache.org/jira/browse/IGNITE-9374 is already in PA
--
Ilya Kasnacheev
2018-08-24 19:11 GMT+03:00 :
> Hi Ignite Developer,
>
> I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed.
> I hope you can help.
>
> *New test failure in master
> TcpDiscoverySslT
Github user alamar closed the pull request at:
https://github.com/apache/ignite/pull/4614
---
Alexei Scherbakov created IGNITE-9380:
-
Summary: Assertion in TxRollbackOnTimeoutTest
Key: IGNITE-9380
URL: https://issues.apache.org/jira/browse/IGNITE-9380
Project: Ignite
Issue Type: B
Taras Ledkov created IGNITE-9379:
Summary: Ignite node hangs after OOM in a thread from thin client
thread pool
Key: IGNITE-9379
URL: https://issues.apache.org/jira/browse/IGNITE-9379
Project: Ignite
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master
TcpDiscoverySslTrustedSelfTest.testOrdinaryNodeFailure
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=25560971
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4617
IGNITE-9374 Replace expired 1-yr certs with new 3-yr ones.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9374
A
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4616
IGNITE-9270 Thread-per-partition Optimization 1
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9270-perf-1
Alter
Ryabov Dmitrii created IGNITE-9378:
--
Summary: Automatical print of critical failures in the PR after
Run All
Key: IGNITE-9378
URL: https://issues.apache.org/jira/browse/IGNITE-9378
Project: Ignite
Ryabov Dmitrii created IGNITE-9377:
--
Summary: Handle print critical failures to the PR
Key: IGNITE-9377
URL: https://issues.apache.org/jira/browse/IGNITE-9377
Project: Ignite
Issue Type: Sub
Ryabov Dmitrii created IGNITE-9376:
--
Summary: Create table with critical failures
Key: IGNITE-9376
URL: https://issues.apache.org/jira/browse/IGNITE-9376
Project: Ignite
Issue Type: Sub-task
Ryabov Dmitrii created IGNITE-9375:
--
Summary: [TC Bot] Highlight critical failures in the PR
Key: IGNITE-9375
URL: https://issues.apache.org/jira/browse/IGNITE-9375
Project: Ignite
Issue Typ
Ilya Kasnacheev created IGNITE-9374:
---
Summary: Certificates used in tests has expired
Key: IGNITE-9374
URL: https://issues.apache.org/jira/browse/IGNITE-9374
Project: Ignite
Issue Type: Bug
Hi, Dmitriy,
Good, I'll create tickets for this steps.
Stable suites are a good idea, but also we need to do some actions when a
flaky test will appear in stable suite of master branch run. To find out a
guilty commit, we should run previous commits on empty TeamCity's queue.
This runs will reduc
asfgit closed pull request #2: Changed algorithm of calculated flaky tests. Now
flaky is test which …
URL: https://github.com/apache/ignite-teamcity-bot/pull/2
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 p
Hi Ignite Developer,
I am MTCGA.Bot, and I've detected some issue on TeamCity to be addressed. I
hope you can help.
*New test failure in master SslParametersTest.testSameCipherSuite
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-7741070898835240150&branc
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4604
---
Ivan Pavlukhin created IGNITE-9373:
--
Summary: MVCC tests fail
Key: IGNITE-9373
URL: https://issues.apache.org/jira/browse/IGNITE-9373
Project: Ignite
Issue Type: Bug
Components: mv
I've rebuilt Ignite from master and tried again, but the behaviour is the
same. If the page is very big (compare with heap size) server node fails
with OOM and the client hangs.
[14:54:06,273][SEVERE][client-connector-#101][ClientListenerProcessor]
Runtime error caught during grid runnable executi
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/4615
IGNITE-9366 SQL system view for node metrics
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite ignite-9366
Alternat
akalash opened a new pull request #2: Changed algorithm of calculated flaky
tests. Now flaky is test which …
URL: https://github.com/apache/ignite-teamcity-bot/pull/2
…changed own status without code changes.
This is an autom
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4614
Ignite gg 14139
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-gg-14139
Alternatively you can review and apply t
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4595
---
Hi Dmitriy,
Sounds like a plan ;) I totally agree.
Just one proposal: I would like to avoid hiding any test failures. 2
separate tables named 'Possible Blockers' and 'Other failures' should be
completely clear. Comment to PR can contain only first category.
We had a private discussion with Anton
GitHub user ygerzhedovich opened a pull request:
https://github.com/apache/ignite/pull/4613
Ignite 6044
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6044
Alternatively you can review and apply th
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4570
---
Nick, Antron, thank you for stepping in.
AFAIK, Ignite cluster can move its state to a new version of Ignite
using persistence only.
Since Ignite v.2.3 persistence is configured on a memory region and
system memory region is not persistence, that means the system
(utility) cache will not be recov
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4612
IGNITE-9237: Random forest optimization
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite IGNITE-9237
Alternatively yo
Github user kukushal closed the pull request at:
https://github.com/apache/ignite/pull/4596
---
Hi Igniters,
I'm a little bit concerned about these failures:
Platform .NET (Long Running)
exe: ExamplesTest.TestRemoteNodes(BinaryModeExample) (fail rate 100,0%)
exe: ExamplesTest.TestRemoteNodes(LinqExample) (fail rate 100,0%)
exe: ExamplesTest.TestRemoteNodes(SqlExample)(fail rate 100,0%)
Hello, Yakov.
Blocker Tickets.
Open:
IGNITE-9184 Mikhail Cherkasov Cluster hangs during concurrent node
restart and continues query registration
IGNITE-8552 VladimirOzerov Unable to use date as primary
key
IGNITE-6980 Aleksey Plekhanov Automatic cancell
Igniters,
We should definitely expand the list of important tickets adding tickets
related to (1) Partition Map Exchange speed up and (2) SQL memory
optimization tickets. Alex Goncharuk, Vladimir, can you please add labels
to corresponding tickets.
Also we have several blocker tickets (mostly rel
Hello!
It is somewhat a part of IEP-20, since I have updated it with this
particular direction.
Regards,
--
Ilya Kasnacheev
2018-08-24 2:56 GMT+03:00 Denis Magda :
> Hi Ilya,
>
> Sounds terrific! Is this part of the following Ignite enhancement proposal?
> https://cwiki.apache.org/confluence/
Hello, Igniters.
I'm testing some java keys with ignite.bat and notice that using more that
four keys lead to internal problem and ignite.bat ignoring them all.
So I created issue https://issues.apache.org/jira/browse/IGNITE-8837 and
investigated , below what i founded
1) inside file ignite.bat
Vasiliy Sisko created IGNITE-9372:
-
Summary: Web console: Failed to execute query with limited page
count
Key: IGNITE-9372
URL: https://issues.apache.org/jira/browse/IGNITE-9372
Project: Ignite
Vasiliy Sisko created IGNITE-9371:
-
Summary: Web console: Failed to open Activity details dialog.
Key: IGNITE-9371
URL: https://issues.apache.org/jira/browse/IGNITE-9371
Project: Ignite
Issue
Vasiliy Sisko created IGNITE-9370:
-
Summary: Web console: Failed to open demo for Queries page.
Key: IGNITE-9370
URL: https://issues.apache.org/jira/browse/IGNITE-9370
Project: Ignite
Issue T
Vasiliy Sisko created IGNITE-9369:
-
Summary: Web console: Collapse of Security token panel on password
change
Key: IGNITE-9369
URL: https://issues.apache.org/jira/browse/IGNITE-9369
Project: Ignite
Vasiliy Sisko created IGNITE-9368:
-
Summary: Web console: Double confirmation of unsaved changes.
Key: IGNITE-9368
URL: https://issues.apache.org/jira/browse/IGNITE-9368
Project: Ignite
Issue
Hi,
Unfortunatelly, scan query doesn't supports timeout at all, neither via
binary client not java API.
OOM can be caused by known bug [1]. Fix is already in master and will be
available in next release.
[1] https://issues.apache.org/jira/browse/IGNITE-8892
On Thu, Aug 23, 2018 at 11:37 PM dmitr
Hello, Dmitriy.
Release page - [1]
> I think it is important to include the links to all important Jira tickets>
> in this thread
Open:
https://issues.apache.org/jira/browse/IGNITE-6980 - Automatic cancelling of
hanging Ignite operations
https://issues.apache.org/jira/browse/IGNITE-5473 - Cre
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4611
Ignite 2.5-master
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5-master
Alternatively you can review and
Hello Pavel,
well this is what Intel claims in the above video. I try to understand
exactly how but the only think I can figure out is that there is some sort
of equivalence between main memory and the 3dx point hardware.
I really really would like to understand this statemetn.
Best Regards
On T
Roman Guseinov created IGNITE-9367:
--
Summary: CPP: ODBC client crashes after executing query with
closed connection
Key: IGNITE-9367
URL: https://issues.apache.org/jira/browse/IGNITE-9367
Project: Ig
Hello, Pavel.
Please, be aware of IGNITE-6055 [1]
I'm edit thin protocol in that ticket.
I can't support changes in Python and PHP clients, because, they are not merged
in master, yet.
Write me, If you have any questions about new fields.
[1] https://issues.apache.org/jira/browse/IGNITE-6055
В
Hi Toru Yabuki,
I've added you to the list of contributors, so now you can assign an issue
to yourself.
Welcome to the Apache Ignite Community!
Sincerely,
Dmitriy Pavlov
P.S. Additional references that should boost your onboarding.
Please subscribe to both dev and user lists:
https://ignite.ap
Hello, Valentin.
> catalog exist in scope of a single IgniteSparkSession> (and therefore single
> IgniteContext and single Ignite instance)?
Yes.
Actually, I was thinking about use case when we have several Ignite
configuration in one XML file.
Now I see, may be this is too rare use-case to su
Aleksey Plekhanov created IGNITE-9366:
-
Summary: SQL system view for node metrics
Key: IGNITE-9366
URL: https://issues.apache.org/jira/browse/IGNITE-9366
Project: Ignite
Issue Type: Task
65 matches
Mail list logo
