Roman Guseinov created IGNITE-9555:
--
Summary: Web Console can stop due to an unexpected message via web
sockets
Key: IGNITE-9555
URL: https://issues.apache.org/jira/browse/IGNITE-9555
Project:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4618
---
Nikolay,
Could you please list the limitations of Phase 1? I'm curious what won't be
supported in 2.7.
--
Denis
On Tue, Sep 11, 2018 at 4:29 PM Nikolay Izhikov wrote:
> > As I understand the plan is to get TDE Phase 1 released in 2.7, right?
>
> Yes. We will release TDE in 2.7
>
> > Could you
Pavel Konstantinov created IGNITE-9554:
--
Summary: Web console demo: do not auto-populate caches created via
SQL
Key: IGNITE-9554
URL: https://issues.apache.org/jira/browse/IGNITE-9554
Project:
Vasiliy Sisko created IGNITE-9553:
-
Summary: Web console: in Demo mode do not polulate caches created
by SQL
Key: IGNITE-9553
URL: https://issues.apache.org/jira/browse/IGNITE-9553
Project: Ignite
Ilya Borisov created IGNITE-9552:
Summary: Web console: add TypeScript support
Key: IGNITE-9552
URL: https://issues.apache.org/jira/browse/IGNITE-9552
Project: Ignite
Issue Type: Improvement
GitHub user DaveWHarvey opened a pull request:
https://github.com/apache/ignite/pull/4732
Mxbeans threads
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/percipiomedia/ignite mxbeans_threads
Alternatively you can review and
Github user DaveWHarvey closed the pull request at:
https://github.com/apache/ignite/pull/4731
---
GitHub user DaveWHarvey opened a pull request:
https://github.com/apache/ignite/pull/4731
Mxbeans thread display improvements
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/percipiomedia/ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4639
---
> As I understand the plan is to get TDE Phase 1 released in 2.7, right?
Yes. We will release TDE in 2.7
> Could you also list what needs to be done at Phase 2 and how much time it
> might take.
Yes, I think Dmitry Ryabov will send Phase 2 design
В Вт, 11/09/2018 в 23:27 +0300, Nikolay
Hello, Denis.
Yes, Vladimir made 2 rounds of review.
I planning to fix all issues with implementation in a few days.
В Вт, 11/09/2018 в 10:40 -0400, Denis Magda пишет:
> Hi Nikolay,
>
> Has anybody started looking into your request? As I understand the plan is
> to get TDE Phase 1 released in
Igor,
I have just commited an improvment to the HandshakeError message
generation algorithm. I hope it is now easier to understand what expects
what in case of binary protocol version mismatch.
Thank you for pointing this out.
On 9/12/18 2:13 AM, Igor Sapego wrote:
I managed to start
GitHub user slukyano opened a pull request:
https://github.com/apache/ignite/pull/4730
Ignite 2.4.6.b4
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.6.b4
Alternatively you can review and
Steve Hostettler created IGNITE-9551:
Summary: Provide support for on-heap/non serialised/read only
caches
Key: IGNITE-9551
URL: https://issues.apache.org/jira/browse/IGNITE-9551
Project: Ignite
Hi Igor,
Did you have to do anything special to make the tests eventually run?
p.
On Tue, Sep 11, 2018 at 9:13 AM, Igor Sapego wrote:
> I managed to start tests, and now I'm getting the following message:
>
> pyignite.exceptions.HandshakeError: Handshake error: Unsupported
> version. Expected
Pavel Vinokurov created IGNITE-9550:
---
Summary: Cache get operation returns null for a lost partition
Key: IGNITE-9550
URL: https://issues.apache.org/jira/browse/IGNITE-9550
Project: Ignite
I managed to start tests, and now I'm getting the following message:
pyignite.exceptions.HandshakeError: Handshake error: Unsupported
version. Expected protocol version: 1.1.0.
It would be useful to print "Unexpected version" itself, because I can
not understand what is the issue.
Best Regards,
David, Maxim!
Thanks a lot for you ideas. Unfortunately, I can't adopt all of them right
now: the scope is much broader than the scope of the change I implement. I
have had a talk to a group of Ignite commiters, and we agreed to complete
the change as follows.
- Blocking instructions in
We need your help to make the Apache Washington DC Roadshow on Dec 4th a
success.
What do we need most? Speakers!
We're bringing a unique DC flavor to this event by mixing Open Source
Software with talks about Apache projects as well as OSS CyberSecurity,
OSS in Government and and OSS Career
Alexand Polyakov created IGNITE-9549:
Summary: control.sh add command to collect information on the
distribution of partitions and reset lost partitions
Key: IGNITE-9549
URL:
Alexei Scherbakov created IGNITE-9548:
-
Summary: Transaction with short timeout is not rolled back on
primary node resulting in blocked PME
Key: IGNITE-9548
URL:
Yury Gerzhedovich created IGNITE-9547:
-
Summary: Document DML operations prohibited inside transaction
Key: IGNITE-9547
URL: https://issues.apache.org/jira/browse/IGNITE-9547
Project: Ignite
Taras Ledkov created IGNITE-9546:
Summary: Document GROUP_CONCAT aggregate function
Key: IGNITE-9546
URL: https://issues.apache.org/jira/browse/IGNITE-9546
Project: Ignite
Issue Type: Task
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4665
---
Hi Nikolay,
Has anybody started looking into your request? As I understand the plan is
to get TDE Phase 1 released in 2.7, right?
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=89067473
Could you also list what needs to be done at Phase 2 and how much time it
might take.
--
SomeFire closed pull request #7: IGNITE-9542: new failure check fix
URL: https://github.com/apache/ignite-teamcity-bot/pull/7
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
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4728
---
Oleg Ignatenko created IGNITE-9545:
--
Summary: IgniteProjectionStartStopRestartSelfTest: misleading
javadocs, required conditions are not described, inconvenient to configure
locally
Key: IGNITE-9545
URL:
GitHub user pavlukhin opened a pull request:
https://github.com/apache/ignite/pull/4728
IGNITE-9516: workaround hanging vacuum after test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9516
SomeFire opened a new pull request #7: IGNITE-9542: new failure check fix
URL: https://github.com/apache/ignite-teamcity-bot/pull/7
This is an automated message from the Apache Git Service.
To respond to the message, please
Alexand Polyakov created IGNITE-9544:
Summary: BinaryOutputStream#writeByte excessive copying after
reaching 1Gb
Key: IGNITE-9544
URL: https://issues.apache.org/jira/browse/IGNITE-9544
Project:
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/4727
MVCC branch
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-mvcc-b3
Alternatively you can review and apply
Roman Kondakov created IGNITE-9543:
--
Summary: MVCC TX: Add Mvcc atomicity mode to ConfigVariations
tests when full cache API support is implemented.
Key: IGNITE-9543
URL:
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4726
Ignite 2.5.1 p12 pme speedup
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
ignite-2.5.1-p12-pme-speedup
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/4725
IGNITE-7764: MVCC TX: make cache basic operations support Mvcc tx mode.
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user ygerzhedovich opened a pull request:
https://github.com/apache/ignite/pull/4724
IGNITE-9519: PK as complex type should can be keep at inline index
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/4723
IGNITE-9249
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9249
Alternatively you can review and apply these
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4721
---
asfgit closed pull request #3: IGNITE-9333 Add statistics page
URL: https://github.com/apache/ignite-teamcity-bot/pull/3
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
Dmitriy Pavlov created IGNITE-9542:
--
Summary: Ignite TC bot: provide separated base/current branch
history for PR page
Key: IGNITE-9542
URL: https://issues.apache.org/jira/browse/IGNITE-9542
Reliability of ignite is very important to me, so please consider following
idea:
- Important threads as WAL writer (as a sample of any critical thread)
must not do any blocking action, by this way:
- WAL thread must be management thread for all WAL operations
- Child, worker thread of WAL
Nikolai Kulagin created IGNITE-9541:
---
Summary: Add the comparison for two general statistics "RunAll"
for master in the date interval
Key: IGNITE-9541
URL: https://issues.apache.org/jira/browse/IGNITE-9541
Hello!
Thank you for the clarifications! Your change looks good to me now.
Regards,
--
Ilya Kasnacheev
вт, 11 сент. 2018 г. в 5:53, Roman Shtykh :
> Ilya,
>
> The "latest" version is the default, and resolved by
> https://ignite.apache.org/latest which is used by our web site when a
> user
Andrew Mashenkov created IGNITE-9540:
Summary: MVCC TX: make cache invoke\invokeAll operations support
Mvcc tx mode.
Key: IGNITE-9540
URL: https://issues.apache.org/jira/browse/IGNITE-9540
Great,
Let us know if you need any kind of help from the community.
Best Regards,
Igor
On Tue, Sep 11, 2018 at 10:48 AM Pavel Tupitsyn
wrote:
> Awesome!
> I've filed a JIRA ticket [1], please assign to yourself, click Start
> Progress, and follow the contribution path [2].
> Looking forward
1) I meant auto-generated doc, this page: [1]. By the way,
many methods do not have any description as well.
2) You can, for example, print object as you generate and
then get them from cache.
3) Yes, 10800 should be the default port.
4) You are right, I've just used server with SSL
Igor Seliverstov created IGNITE-9538:
Summary: MVCC TX: Send partition update counters to backup nodes
on prepare state.
Key: IGNITE-9538
URL: https://issues.apache.org/jira/browse/IGNITE-9538
PetrovMikhail created IGNITE-9539:
-
Summary: Add SQL column precision existence check if scale
parameter is setted
Key: IGNITE-9539
URL: https://issues.apache.org/jira/browse/IGNITE-9539
Project:
GitHub user avplatonov opened a pull request:
https://github.com/apache/ignite/pull/4722
IGNITE-9531: ZookeeperDiscovery testClientReconnect is flaky in master
You can merge this pull request into a Git repository by running:
$ git pull
Hello, Denis.
Thanks for providing reproducers for bugs!
I taked a look at your project and be able to reproduce some of errors.
I will create a ticket and start investigation in a next few days.
В Вт, 11/09/2018 в 12:28 +0300, Dmitriy Pavlov пишет:
> Hi Denis,
>
> Thank you for bringing this
Alexey, Ivan,
Agree. Keeping strong references to the Thread object is the source of
memory leak with ThreadLocals variables
and the values that it stores. ThreadLocalMap is bound to the Thread
lifespan [1], so I think when we are using
everything right all will be GC'ed correctly.
Is this memory
Dmitriy,
Could you point to some piece of code implementing described pattern?
2018-09-11 13:02 GMT+03:00 Павлухин Иван :
> Alex,
>
> ThreadLocal subclass is used in IgniteH2Indexing for simple access to H2
> Connection from current thread. Such subclass has a capability to create
> connection
Alex,
ThreadLocal subclass is used in IgniteH2Indexing for simple access to H2
Connection from current thread. Such subclass has a capability to create
connection if one does not exist, so obtaining connection is merely
ThreadLocal.get. Also there are scheduled routines to cleanup connections
and
SomeFire opened a new pull request #6: IGNITE-9377 Handle print crit failures
from RunAll to the JIRA ticket
URL: https://github.com/apache/ignite-teamcity-bot/pull/6
This is an automated message from the Apache Git
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4717
---
Hi Ivan,
I can imagine cases with temporary native or heap byte buffers in thread
locals used for IO operations.
These buffers are often Thread Local and I find it to be a perfectly ok
case.
вт, 11 сент. 2018 г. в 11:00, Alexey Goncharuk :
> Ivan,
>
> Can you elaborate on the issue with the
Hi Tam Manh Nguyen,
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
пн, 10 сент. 2018 г. в 23:23, Tâm Nguyễn Mạnh :
> Hi,
>
> I just registered. Here is my jira account:
Roman Kondakov created IGNITE-9537:
--
Summary: .NET: Change MVCC enabled configuration.
Key: IGNITE-9537
URL: https://issues.apache.org/jira/browse/IGNITE-9537
Project: Ignite
Issue Type:
Hi Denis,
Thank you for bringing this here and for your efforts to reproduce it.
Would you like to create an issue and contribute these test into Ignite
code base?
If you would like to proceed with the patch submission process, please
sign-in to Apache JIRA and share your JIRA username, I will
Roman Kondakov created IGNITE-9536:
--
Summary: CPP/ODBC: Change MVCC enabled configuration.
Key: IGNITE-9536
URL: https://issues.apache.org/jira/browse/IGNITE-9536
Project: Ignite
Issue
GitHub user ibessonov opened a pull request:
https://github.com/apache/ignite/pull/4721
IGNITE-9535 ClientChangeGlobalStateComputeRequest is missing @GridInternal
annotation
You can merge this pull request into a Git repository by running:
$ git pull
Ivan Bessonov created IGNITE-9535:
-
Summary: ClientChangeGlobalStateComputeRequest is missing
@GridInternal annotation
Key: IGNITE-9535
URL: https://issues.apache.org/jira/browse/IGNITE-9535
Project:
GitHub user udaykale opened a pull request:
https://github.com/apache/ignite/pull/4720
IGNITE-9532 Binary mode for Ignite Queue
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/udaykale/ignite IGNITE-9532
Alternatively you can
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4704
---
Ilya Suntsov created IGNITE-9534:
Summary: Wrong error message in bin/include/functions.sh
Key: IGNITE-9534
URL: https://issues.apache.org/jira/browse/IGNITE-9534
Project: Ignite
Issue Type:
Dmitriy Gladkikh created IGNITE-9533:
Summary: Monitoring of meta-data discrepancies on all cluster
nodes at runtime
Key: IGNITE-9533
URL: https://issues.apache.org/jira/browse/IGNITE-9533
Uday Kale created IGNITE-9532:
-
Summary: Binary mode for Ignite Queue
Key: IGNITE-9532
URL: https://issues.apache.org/jira/browse/IGNITE-9532
Project: Ignite
Issue Type: New Feature
GitHub user xtern reopened a pull request:
https://github.com/apache/ignite/pull/4711
IGNITE-6346
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-6346
Alternatively you can review and apply these changes as
Github user xtern closed the pull request at:
https://github.com/apache/ignite/pull/4711
---
Alexey Platonov created IGNITE-9531:
---
Summary: ZookeeperDiscovery testClientReconnect is flaky in master
Key: IGNITE-9531
URL: https://issues.apache.org/jira/browse/IGNITE-9531
Project: Ignite
Ivan,
Can you elaborate on the issue with the thread local cleanup you've faced?
вт, 11 сент. 2018 г. в 9:13, Павлухин Иван :
> Guys,
>
> As we know ThreadLocal is an instrument which should be used with great
> care. And I recently faced with problems related to proper cleanup of
> ThreadLocal
Roman Kondakov created IGNITE-9530:
--
Summary: MVCC TX: Local caches support.
Key: IGNITE-9530
URL: https://issues.apache.org/jira/browse/IGNITE-9530
Project: Ignite
Issue Type: Task
Hello everybody!
I found a few bugs in the actual version of Apache Ignite Spark (2.6.0) and
described in my GitHub: https://github.com/x-x-z/IgniteSparkBugs
I wrote a test for each case:
Awesome!
I've filed a JIRA ticket [1], please assign to yourself, click Start
Progress, and follow the contribution path [2].
Looking forward to a pull request from you!
[1] https://issues.apache.org/jira/browse/IGNITE-9529
[2]
Pavel Tupitsyn created IGNITE-9529:
--
Summary: .NET: Thin client: Implement TextQuery
Key: IGNITE-9529
URL: https://issues.apache.org/jira/browse/IGNITE-9529
Project: Ignite
Issue Type:
Igor,
I literally followed the steps you describe, but unfortunately could not
reproduce the error.
The only clue I got is that your site-packages already have the newer
version of attrs (18.2.0 against 18.1.0 as of pyignite requirements).
But this should not be an issue, since
Guys,
As we know ThreadLocal is an instrument which should be used with great
care. And I recently faced with problems related to proper cleanup of
ThreadLocal which is not needed anymore. In my opinion the best thing (in
ideal world) is to get rid of ThreadLocal where possible, but I guess that
78 matches
Mail list logo
