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: Impr
Nikolay, thank you for fixing
чт, 27 дек. 2018 г. в 23:00, Dmitriy Pavlov :
> Thanks to Michail Petrov we have now TC Bot notifications on compilation
> failures.
>
>
> чт, 27 дек. 2018 г. в 22:07, :
>
>> Hi Igniters,
>>
>> I've detected some new issue on TeamCity to be handled. You are more
>>
Thanks to Michail Petrov we have now TC Bot notifications on compilation
failures.
чт, 27 дек. 2018 г. в 22:07, :
> Hi Igniters,
>
> I've detected some new issue on TeamCity to be handled. You are more than
> welcomed to help.
>
> If your changes can lead to this failure(s): We're grateful tha
Evgenii Zhuravlev created IGNITE-10838:
--
Summary: Ignite wrap byte[] value with
UserCacheObjectByteArrayImpl before saving it and copying the whole array
Key: IGNITE-10838
URL: https://issues.apache.org/jira
Max Shonichev created IGNITE-10837:
--
Summary: control.sh --baseline should output node IP addresses
Key: IGNITE-10837
URL: https://issues.apache.org/jira/browse/IGNITE-10837
Project: Ignite
Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
If your changes can lead to this failure(s): We're grateful that you were a
volunteer to make the contribution to this project, but things change and you
may no longer be able to finalize
Folks,
What are the current timeouts? We need to know the probability of failures
in dev environment. This affect usability.
--
Denis
On Thu, Dec 27, 2018 at 4:59 AM Alexey Goncharuk
wrote:
> Nikolay,
>
> Yes, the fix is already in master. Looks like I was wrong, in your case
> failure handler
Ilya,
Why do we use -J in general? Is it used to pass a specific type of
parameters? I know -D or - X but can't recall what -J is supposed to be
used for.
--
Denis
On Thu, Dec 27, 2018 at 6:34 AM Ilya Kasnacheev
wrote:
> Hello!
>
> I have debugged this issue. It seems to be a JVM bug on Windo
Hi, Ilya!
It looks like Spring *ThreadPoolTaskScheduler* is bounded to JDK's
*ScheduledThreadPoolExecutor*, so to launch scheduled tasks on public pool
we need provide *ScheduledThreadPoolExecutor* for Public pool. Currently I
see we create Public pool executor as *IgniteThreadPoolExecutor* and it
Hello!
I have debugged this issue. It seems to be a JVM bug on Windows, where JVM
will silently fail to run program's main class:
java HelloWorld -v -J1 -J2 - works
java HelloWorld -v -J1 -J2 -J3 - fails
java -Dfile.encoding=UTF-8 HelloWorld -v -J1 -J2 -J3 - works
java -Dfile.encoding=UTF-8 Hello
Nikolay,
Yes, the fix is already in master. Looks like I was wrong, in your case
failure handler is triggered by 'Node is stopping: grid-2'. Can you please
share the full trace?
чт, 27 дек. 2018 г. в 12:41, Nikolay Izhikov :
> Alexey
>
> Fix for this issue already in master?
> I run tests on c
Namrata Bhave created IGNITE-10835:
--
Summary: Test failure in IgnitePdsReplacementNativeIoTest
Key: IGNITE-10835
URL: https://issues.apache.org/jira/browse/IGNITE-10835
Project: Ignite
Issue
Alexander Lapin created IGNITE-10836:
Summary: Add documentation for jdbc thin query cancel
Key: IGNITE-10836
URL: https://issues.apache.org/jira/browse/IGNITE-10836
Project: Ignite
Issue
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:
Anton Dmitriev created IGNITE-10834:
---
Summary: [ML] Add NamedVectors to replace HashMap in Model
Key: IGNITE-10834
URL: https://issues.apache.org/jira/browse/IGNITE-10834
Project: Ignite
Is
Dmitriy Pavlov created IGNITE-10832:
---
Summary: [TC Bot] Auto-trigger check win agents availability
before triggering a build
Key: IGNITE-10832
URL: https://issues.apache.org/jira/browse/IGNITE-10832
Ilya Kasnacheev created IGNITE-10831:
Summary: Document update/delete queries in Spring Data 2.0
Key: IGNITE-10831
URL: https://issues.apache.org/jira/browse/IGNITE-10831
Project: Ignite
Vyacheslav Daradur created IGNITE-10830:
---
Summary: Return back semantic of
GridServiceProcessor#ServiceTopologyCallable to avoid possible serialization
issues
Key: IGNITE-10830
URL: https://issues.apache.or
Alexey
Fix for this issue already in master?
I run tests on current master.
> Should we somehow announce it on the user-list or highlight on readme.io?
I don't think our users will be happy to users stuck with this behavior in
production.
Am I understand you correctly:
If someone use 2.7. relea
Hi Nikolay,
This is the issue I mentioned in "Critical worker threads liveness checking
drawbacks" topic which I was expecting to be included to Ignite 2.7, but it
was not. To workaround the issue, you should set
DataStorageConfiguration#setCheckpointReadLockTimeout to 0.
Should we somehow announ
Igor Seliverstov created IGNITE-10829:
-
Summary: MVCC TX: Lazy query execution for query enlists.
Key: IGNITE-10829
URL: https://issues.apache.org/jira/browse/IGNITE-10829
Project: Ignite
Hello, Igniters.
I run into issue with critical system worker failure handler.
I just run `IgniteDataFrameSuite` and it terminates on random test.
My laptop doesn't have bleeding edge hardware, so tests can take
significant amount of time.
Looks like our watch dog too aggressive on development env
22 matches
Mail list logo