GitHub user ezagumennov opened a pull request:
https://github.com/apache/ignite/pull/4034
Ignite 7766
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7766
Alternatively you can review and apply thes
Andrey Aleksandrov created IGNITE-8535:
--
Summary: WebConsole configuration over HTTPs guide should be
documented
Key: IGNITE-8535
URL: https://issues.apache.org/jira/browse/IGNITE-8535
Project:
GitHub user ezagumennov opened a pull request:
https://github.com/apache/ignite/pull/4035
IGNITE-7766 test should retry, not fail
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7766
Alternatively y
Github user ezagumennov closed the pull request at:
https://github.com/apache/ignite/pull/4034
---
Alexey Kuznetsov created IGNITE-8536:
Summary: DirectMemoryRegion: Introduce checkpoint buffer
configuration and improve logging o start
Key: IGNITE-8536
URL: https://issues.apache.org/jira/browse/IGNITE-8536
Alexey Kuznetsov created IGNITE-8537:
Summary: Web Console: Proof-read texts
Key: IGNITE-8537
URL: https://issues.apache.org/jira/browse/IGNITE-8537
Project: Ignite
Issue Type: Improvemen
Alexey Kuznetsov created IGNITE-8538:
Summary: Web Console: Refactor redirecting to default state.
Key: IGNITE-8538
URL: https://issues.apache.org/jira/browse/IGNITE-8538
Project: Ignite
Alexey Kuznetsov created IGNITE-8539:
Summary: Web Console: add additional checks to prevent
unauthorized web-socket connection.
Key: IGNITE-8539
URL: https://issues.apache.org/jira/browse/IGNITE-8539
Hi Maxim,
I observe the same, Cache 6 critical recent fails: 18,0% [9 fails / 50 runs]
I hope Aleksei Scherbakov can help here. Alexey, please step in.
Sincerely,
Dmitriy Pavlov
вс, 20 мая 2018 г. в 20:37, Maxim Muzafarov :
> Hello Igniters,
>
> Have anyone noticed a lot of execution timeouts
GitHub user anton-vinogradov opened a pull request:
https://github.com/apache/ignite/pull/4036
IGNITE-8446 Ability to check and completely fill transactions on creaâ¦
â¦tion
Signed-off-by: Anton Vinogradov
You can merge this pull request into a Git repository by running:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3748
---
Igniters,
Fix is ready.
Code checked by Nikolay Izhikov, all issues fixed
Code benchmarked by Ilya Suntsov, no drop found.
Fix *affects public API*, so I'm proposing everyone interested check it.
Issue: https://issues.apache.org/jira/browse/IGNITE-8446
PR: https://github.com/apache/ignite/pull/40
Anton Kalashnikov created IGNITE-8540:
-
Summary: Slow rebalance with asynchronous eviction
Key: IGNITE-8540
URL: https://issues.apache.org/jira/browse/IGNITE-8540
Project: Ignite
Issue Ty
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4037
IGNITE-8540 removing persistent files for joined node if it is not inâ¦
⦠baseline
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/a
Cross-posting to user list.
Hi Folks,
could you please comment?
Sincerely,
Dmitiry Pavlov
пн, 21 мая 2018 г. в 7:41, zhouxy1123 :
>
> hi ， How dose ignite implement concurrent control in transaction？
> Since Ignite support Read Repeat isolation，so in a transaction lock
> protocol
> is tow phas
Taras Ledkov created IGNITE-8541:
Summary: Auth: username case sensitive/insensitive behavior is
invalid
Key: IGNITE-8541
URL: https://issues.apache.org/jira/browse/IGNITE-8541
Project: Ignite
hi ， How dose ignite implement concurrent control in transaction？
Since Ignite support Read Repeat isolation，so in a transaction lock protocol
is tow phase with respect to exclusive lock and well-formed. Does Ignite
implement tow phase lock and granule lock to prevent phantom read.Besides
Dose
Hi,
Probably answers can be found here
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Key-Value+Transactions+Architecture
Sincrely,
Dmitriy Pavlov
пн, 21 мая 2018 г. в 14:46, zhouxy1123 :
> hi ， How dose ignite implement concurrent control in transaction？
> Since Ignite support Read
Aleksey Zinoviev created IGNITE-8542:
Summary: [ML] Add OneVsRest Trainer to handle cases with multiple
class labels in dataset
Key: IGNITE-8542
URL: https://issues.apache.org/jira/browse/IGNITE-8542
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4008
---
Peter Ivanov created IGNITE-8543:
Summary: Node.js tests count with debug on/off differs
Key: IGNITE-8543
URL: https://issues.apache.org/jira/browse/IGNITE-8543
Project: Ignite
Issue Type: Bu
Anton, I have objections. Please do not merge unless we agree on details.
1. You use internal API in public event, i.e. you cannot have user
accessing to IgniteInternalTx instance through TxEvent.
2. Throwing runtime errors from listener is not documented and I doubt if
it can be fully supported i
Hi Yakov,
I've checked this code and IgniteCacheTestSuite6 includes TxLabelTest, so
point 3 can be considered as solved.
Sincerely,
Dmitriy Pavlov
пн, 21 мая 2018 г. в 16:05, Yakov Zhdanov :
> Anton, I have objections. Please do not merge unless we agree on details.
>
> 1. You use internal API
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3082
---
Ok, then it probably might have been created before this PR. Anyway, I
would not bother too much about pt 3.
--Yakov
2018-05-21 16:15 GMT+03:00 Dmitry Pavlov :
> Hi Yakov,
>
> I've checked this code and IgniteCacheTestSuite6 includes TxLabelTest, so
> point 3 can be considered as solved.
>
> Sin
hi Dmitriy Pavlov ,
thanks for your reply,
I read the doc , and I find that in RR isolation ,there is just one kind of
lock.
So Ignite dose not support share lock ? And dose Ignite not support granule
lock?
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
GitHub user vveider opened a pull request:
https://github.com/apache/ignite/pull/4038
IGNITE-8526 Create web-agent docker image for k8s deployment
* added web-agent separate docker image build
* refactored and unified docker specifications layout
You can merge this pull reques
Yakov, thank's for deep check.
>> I think that we should think about some other solution instead of
altering
>> event sub-system.
Thank's to your comments now I see that solution is not perfect.
How about to create
interface TransactionsValidator {
boolean validate(IgniteTransactions tx){
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3844
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/3986
---
Anton,
The change looks very questionable. We cannot be adding configuration
validators for every piece of Ignite API. What is it you are trying to
achieve?
D.
On Mon, May 21, 2018 at 7:22 AM, Anton Vinogradov wrote:
> Yakov, thank's for deep check.
>
> >> I think that we should think about so
Pavel Kovalenko created IGNITE-8544:
---
Summary: WAL disabling during rebalance mechanism uses wrong
topology version in case of exchanges merge
Key: IGNITE-8544
URL: https://issues.apache.org/jira/browse/IGNITE-8
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/4039
IGNITE-8544 Use exchange result topology version for local wal state change
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-igni
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4030
---
Ilya Kasnacheev created IGNITE-8545:
---
Summary: If queryParallelism in nodes' caches configurations
differ, query may hang, assert or return incomplete results
Key: IGNITE-8545
URL: https://issues.apache.org/jira
Dmitriy,
Main idea is to restrict transaction creation in case label or timeout are
not set.
But there can be variations, for example label should fit some regexp or
timeout should be between 30 and 5000 ms.
That's not easy to restrict this at user code when you have dozens of
libraries written b
One more case is to analize and log tx's creators info without tx creation
restriction.
This is very important feature on huge system trial period when you may
want to check who creates tx, tx content and configuration.
For example you may want to log stacktrace for any tx without meta or with
empt
Roman Guseinov created IGNITE-8546:
--
Summary: Permission denied while copying OPTION_LIBS on Openshift
Key: IGNITE-8546
URL: https://issues.apache.org/jira/browse/IGNITE-8546
Project: Ignite
GitHub user antkr opened a pull request:
https://github.com/apache/ignite/pull/4040
1.9 ignite reject threads
For test purposes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
1.9-ignite-reject-threads
Al
Ilya Kasnacheev created IGNITE-8547:
---
Summary: Deserialization of Enum values as anonymous classes may
cause deadlock
Key: IGNITE-8547
URL: https://issues.apache.org/jira/browse/IGNITE-8547
Project:
It works, thanks Vitaliy!
p.
On Sun, May 20, 2018 at 1:16 PM, Vitaliy Osipov
wrote:
> Pavel. Hi
>
> The necessary rights have been added. Check please.
>
> On 19 May 2018 at 01:48, Pavel Petroshenko wrote:
>
>> Thank you, Denis! I need to have a role to be able to temporary rearrange
>> builds
GitHub user agura opened a pull request:
https://github.com/apache/ignite/pull/4041
Apache ignite 2.5 release notes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agura/incubator-ignite release_notes
Alternatively you can revie
Denis Magda created IGNITE-8548:
---
Summary: Make Apache Ignite JCache 1.1 specification compliant
Key: IGNITE-8548
URL: https://issues.apache.org/jira/browse/IGNITE-8548
Project: Ignite
Issue Ty
Igniters,
Eventually, JCache was relicensed to Apache 2.0 and released 1.1 version:
https://groups.google.com/forum/#!topic/jsr107/BC1qKqknzKU
Is there anyone interested in upgrading Ignite to the new version for the
next release?
https://issues.apache.org/jira/browse/IGNITE-8548
--
Denis
Thanks for the details. Please go ahead and implement it if you'd like.
--
Denis
On Sat, May 19, 2018 at 3:42 AM, uday kale wrote:
> The ELB discovery currently supports classic load balancers only. What I
> want to add is ELB discovery for Application load balancers too. For
> difference betwe
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4042
IGNITE-8547 Use JVM serialization for enum values with OptimizedMarshaller
.., avoid deadlock.
Also IGNITE-5087 Enum comparison fails after marshal-unmarshal with
BinaryMarshaller.
You can
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4039
---
GitHub user 1vanan opened a pull request:
https://github.com/apache/ignite/pull/4043
IGNITE-8406
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1vanan/ignite IGNITE-8406
Alternatively you can review and apply these changes as t
Prachi Garg created IGNITE-8549:
---
Summary: Include SSL related parameters for JDBC/ODBC
Key: IGNITE-8549
URL: https://issues.apache.org/jira/browse/IGNITE-8549
Project: Ignite
Issue Type: Task
Stanislav Lukyanov created IGNITE-8550:
--
Summary: CacheAbstractJdbcStore expects merge to always return 1
but MySQL may also return 2 or 0
Key: IGNITE-8550
URL: https://issues.apache.org/jira/browse/IGNITE-85
Hi,
FYI, HZ also has NodeJs client: https://github.com/
hazelcast/hazelcast-nodejs-client
May be it is worth to take a look?
--
Alexey Kuznetsov
Spark released its newest version 2.3.0 on Feb 28th, so I'd like to open a
discussion about whether we should upgrade Ignite Spark module to to the
latest version.
In the release notes
https://spark.apache.org/releases/spark-release-2-3-0.html, spark 2.3
introduced many useful new features and as w
Thanks Denis
On Mon, May 21, 2018 at 10:46 PM Denis Magda wrote:
> Thanks for the details. Please go ahead and implement it if you'd like.
>
> --
> Denis
>
> On Sat, May 19, 2018 at 3:42 AM, uday kale wrote:
>
> > The ELB discovery currently supports classic load balancers only. What I
> > want
53 matches
Mail list logo
