Can you please provide an update
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I see ignite-spring 2.7.6 comes with 4.3.18.RELEASE. If I exclude these jars
and maintain 5.x.RELEASE, it is not working. So does ignite supports only
till 4.x release?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi All,
this email is for info sake I put together a document that covers how to
set up Ignite on AWS and fixed missing code (
https://aws.amazon.com/blogs/big-data/real-time-in-memory-oltp-and-analytics-with-apache-ignite-on-aws/)
in this blog, which can be useful for Quick POC.
Working Code to
Unable to upload since the projects are larger than 5 MB. Can you share your
google id?
Thanks,
Naushad
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
In my otherwise stably running grid (on 2.7.5) I sometimes see intermittent
GridDhtPartitionsExchangeFuture warning. This warning the occurs periodically
and then goes away after some time. I couldn't find any documentation or other
threads about this warning and its implications.
* What is
Here is a log of the failed start up:
cp: can't stat '/opt/ignite/apache-ignite/libs/optional/ignite-spring': No such
file or directory
cp: can't stat '/opt/ignite/apache-ignite/libs/optional/ignite-indexing': No
such file or directory
[21:54:08]__
[21:54:08] /
I also see this printing every few seconds on my client application...
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi Accepted
incoming communication connection [locAddr=/xxx.xxx.xxx.68:47101,
rmtAddr=/xxx.xxx.xxx.82:49816
On Mon, 21 Oct 2019 at 12:04, John Smith wrote:
> Hi,
I should have mentioned I'm using String->BinaryObject in my cache. My binary
object itself has a large number of field->value pairs (a few thousand). As I
run my ingestion jobs using datastreamers, depending on the job type some new
fields might be added to the binary object but eventually
All,
Installation of JDK 1.8 solved all issues. Thanks Pavel.
Regards,
Sudhir
On Monday, October 21, 2019, Pavel Tupitsyn wrote:
> > What is interesting is that with this setup it is working fine on one
> machine but same does not work for other machine. What is missing here?
>
> Ignite.NET
Hi, thanks. I already made sure that each ignite VM runs on a separate host
within our cloud. I'm not doing any of that migration stuff.
Also recently disabled metrics igniteConfig.setMetricsLogFrequency(0); Just
to make sure it doesn't get too chatty. But i doubt this would affect it...
Should
Thanks Anton for the response. I'm using 2.7.5. I think you correctly
identified the issue - I do see MetadataUpdateProposedMessage objects inside.
What is not very clear is what the trigger for this is, and what the work
around is? What would help is, if you could help with explaining the
Justin,
Good to know that. Some comments:
> Their SQL is built on top of the key-value interface so they get parallel
> optimistic transactions "for free"
AFAIK Cockroach transactions does not use RocksDB transactional
capabilities at all. Moreover do not know if your case is possible
with
Kurt,
I tried reproducing this issue using your data, but I didn’t manage to make the
query for id return only one entry.
What version of Ignite do you use? How did you insert the data? SQL or cache
API?
Denis
On 17 Oct 2019, 15:21 +0300, Kurt Semba , wrote:
> Hi Denis,
>
> The cache was
Pavel, Thanks again.
I will look into NLog integrations.
On Monday, October 21, 2019, Pavel Tupitsyn wrote:
> THE way to configure Ignite.NET logging is to use NLog/log4net
> integrations and their corresponding configuration mechanisms.
> Please see the docs:
>
THE way to configure Ignite.NET logging is to use NLog/log4net integrations
and their corresponding configuration mechanisms.
Please see the docs:
https://apacheignite-net.readme.io/docs/logging
The piece of code above was just easier to explain :)
On Mon, Oct 21, 2019 at 4:27 PM Sudhir Patil
Pavel, Thanks for insights.
1st point - sure I will check out those keys over different machine. That
check on java is looks simple and clean in ignite. :)
2nd point - i will add this logging & try it out. Is this THE way to enable
logging of ignite.net internals like different log statement
> What is interesting is that with this setup it is working fine on one
machine but same does not work for other machine. What is missing here?
Ignite.NET detects Java installation on Windows by checking JAVA_HOME env
var and then the following registry keys:
- Software\JavaSoft\Java Runtime
Hi Biswajee,
This is configured only in the section that you sent. Unless you redefine
this in your java code.
Are you sure that you actually set different names for ${S3_BUCKET_NAME}?
Can you send logs to check current behaviour?
On Mon, Oct 21, 2019 at 1:17 PM Rout, Biswajeet
wrote:
> Hi,
>
Pavel, Thanks. :)
- for jdk version = Ok we have 1.8 also installed but java_home and path
variables are set to folder path of 1.7. What is interesting is that with
this setup it is working fine on one machine but same does not work for
other machine. What is missing here?
- for log files for
> jdk1.7
Please install Java 8 or newer
> This is windows environment variable. You can point it to any directory
you want.
Evgeniy, IGNITE_HOME is not required for Ignite.NET, most users do not use
it.
On Mon, Oct 21, 2019 at 3:26 PM Evgeniy Rudenko
wrote:
> This is windows environment
This is windows environment variable. You can point it to any directory you
want.
On Mon, Oct 21, 2019 at 3:21 PM Sudhir Patil
wrote:
> Thanks Evginy. What is Ignite_home directory?
>
> Regards,
> Sudhir
>
> On Monday, October 21, 2019, Evgeniy Rudenko
> wrote:
>
>> Logs can be found in your
Thanks Evginy. What is Ignite_home directory?
Regards,
Sudhir
On Monday, October 21, 2019, Evgeniy Rudenko wrote:
> Logs can be found in your ${IGNITE_HOME}\work\log directory.
>
> On Mon, Oct 21, 2019 at 2:58 PM Alexandr Shapkin
> wrote:
>
>> Hello!
>>
>> Please, check that you are using the
Hello!
I think that you should use DataStreamer to populate data. Should remove
most of this discrepancy.
Regards,
--
Ilya Kasnacheev
вс, 20 окт. 2019 г. в 20:02, Simin Eftekhari :
> Hello Everyone,
>
> I am new to apache ignite. I'd appreciate your help with the following
> question.
>
> I
Thanks Alexandr.
Yes I check about those a reply here. This is stage as with same
setup values ignite is working fine on one machine and on another machine
even with same values it is giving said error.
On Monday, October 21, 2019, Alexandr Shapkin wrote:
> Hello!
>
> Please, check that you
Update : Even with below environment variable values still same error is
received.
I did checked on java_home environment variable and it is set properly to
c:/program files/java/jdk1.7.xxX/bin/server
Also path variable do have value for java viz. C:/program
files/java//jdk1.7.xxx/bin
C:/program
Logs can be found in your ${IGNITE_HOME}\work\log directory.
On Mon, Oct 21, 2019 at 2:58 PM Alexandr Shapkin wrote:
> Hello!
>
> Please, check that you are using the right JDK version (8+).
>
> The proper version is set for JAVA_HOME, and you do not use the JvmDllPath
> configuration.
>
> Is
Oh, I see. Thank you.
在 2019/10/21 下午4:30, Evgeniy Rudenko 写道:
Doc is correct. Each ExpiryPolicy contains 3 methods that define it's
behaviour based on used operation:
getExpiryForCreation()
getExpiryForAccess()
getExpiryForUpdate()
On Sun, Oct 20, 2019 at 3:20 AM 李玉珏@163 <18624049...@163.com
Hello!
Please, check that you are using the right JDK version (8+).
The proper version is set for JAVA_HOME, and you do not use the JvmDllPath
configuration.
Is it possible that you have multiple Java installations?
From: Sudhir Patil
Sent: Monday, October 21, 2019 2:25 PM
To:
Hello!
Can you publish a complete Spring reproducer project?
The only thing I have noticed outright is that you call load() before the
app (and Ignite) is started.
Regards,
--
Ilya Kasnacheev
пт, 18 окт. 2019 г. в 23:51, niamin :
> Looks like it is something with the using ARInvoiceId as
Hi,
I would suggest you to deploy ignite server nodes on separate machines.
If you are using virtualized infrastructure, I would suggest you to
create two separate VMs. Ideally each VM should be running on a
different hypervisor with enough headroom so that both VMs don't compete
for
Hello!
Ignite operations will use built-in locks even if you don't explicitly use
any. If you have uncommitted transactions or something like that,
checkpoint can't start (and other operations are waiting for it too).
How big are we talking about? I recommend capturing several thread dumps
after
I am using nuget package Apache.Ignite 2.7.5
Regards,
Sudhir
On Monday, October 21, 2019, Sudhir Patil wrote:
> Hi All,
>
> I am getting this error when Ignition.Start method is called. Exception
> message says - JNI_CreateJavaVM failed: VersionError.
>
> I don't have any log file for this or
Hi All,
I am getting this error when Ignition.Start method is called. Exception
message says - JNI_CreateJavaVM failed: VersionError.
I don't have any log file for this or pleas kelet me know where to get log
file.
Please help me on this issue.
Regards,
Sudhir
--
Thanks & Regards,
Sudhir
Hi,
I have used the S3 discovery mechanism to discovers the node in the ignite
cluster.
I have used two different buckets for two different instance of my
application. Where as I can see irrespective of bucket, the nodes are
discovering each other and forming clusters.
Is there any configuration
Hi Conrad
All caches in the group should have the same partitionLossPolicy. Cache
with different partitionLossPolicy should not be allowed to join the group.
Could you tell what version of Ignite you are using. Also could you attach
full logs and full xml configurations to check.
On Mon, Oct
Doc is correct. Each ExpiryPolicy contains 3 methods that define it's
behaviour based on used operation:
getExpiryForCreation()
getExpiryForAccess()
getExpiryForUpdate()
On Sun, Oct 20, 2019 at 3:20 AM 李玉珏@163 <18624049...@163.com> wrote:
> Hi,
>
> On the following page:
>
>
36 matches
Mail list logo
