tried running everything from the /vagrant directory directly and it
> fails as well so this might actually be a synced folder issue.
>
> Lukas
>
> From: Lukas Steiblys
> Sent: Wednesday, February 18, 2015 1:46 AM
> To: dev@samza.apache.org
> Subject: Re: RocksDBException:
uary 17, 2015 3:25 PM
>
> To: dev@samza.apache.org
> Subject: Re: RocksDBException: IO error: directory: Invalid argument
>
> I deployed it to one of our VMs in Rackspace and it worked fine.
>
> Lukas
>
> -Original Message- From: Ruslan Khafizov
> S
age----- From: Lukas Steiblys
> > Sent: Tuesday, February 17, 2015 3:25 PM
> >
> > To: dev@samza.apache.org
> > Subject: Re: RocksDBException: IO error: directory: Invalid argument
> >
> > I deployed it to one of our VMs in Rackspace and it worked fine.
>
deal solution.
>
> Lukas
>
> -Original Message- From: Lukas Steiblys
> Sent: Tuesday, February 17, 2015 3:25 PM
>
> To: dev@samza.apache.org
> Subject: Re: RocksDBException: IO error: directory: Invalid argument
>
> I deployed it to one of our VMs in Rackspace and it work
n: IO error: directory: Invalid argument
I deployed it to one of our VMs in Rackspace and it worked fine.
Lukas
-Original Message-
From: Ruslan Khafizov
Sent: Tuesday, February 17, 2015 3:11 PM
To: dev@samza.apache.org
Subject: Re: RocksDBException: IO error: directory: Invalid argument
O
I deployed it to one of our VMs in Rackspace and it worked fine.
Lukas
-Original Message-
From: Ruslan Khafizov
Sent: Tuesday, February 17, 2015 3:11 PM
To: dev@samza.apache.org
Subject: Re: RocksDBException: IO error: directory: Invalid argument
On Wed, Feb 18, 2015 at 5:37 AM
ing on the check?
>
> Lukas
>
> -Original Message- From: Chris Riccomini
> Sent: Tuesday, February 17, 2015 1:02 PM
>
> To: dev@samza.apache.org
> Cc: Chris Riccomini
> Subject: Re: RocksDBException: IO error: directory: Invalid argument
>
> Hey Lucas,
>
I could try and built a test job if you can’t reproduce it locally.
Lukas
From: Chris Riccomini
Sent: Tuesday, February 17, 2015 2:19 PM
To: Lukas Steiblys
Cc: dev@samza.apache.org ; Chris Riccomini
Subject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lukas,
Let me try
g a handle to the store, but then I got an error that
> state/engagement-store/Partition 0 was not found.
>
> Lukas
>
> -Original Message- From: Chris Riccomini
> Sent: Tuesday, February 17, 2015 1:47 PM
> To: dev@samza.apache.org
> Cc: Chris Riccomini
> Subject: Re:
Riccomini
Sent: Tuesday, February 17, 2015 1:47 PM
To: dev@samza.apache.org
Cc: Chris Riccomini
Subject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lukas,
Hmm.
1. I'm running it as another user, but in the user's home directory so it
has no problem writing or reading
gt; Sent: Tuesday, February 17, 2015 1:37 PM
>
> To: dev@samza.apache.org
> Cc: Chris Riccomini
> Subject: Re: RocksDBException: IO error: directory: Invalid argument
>
> 1. I'm running it as another user, but in the user's home directory so it
> has no problem writing or re
1:37 PM
To: dev@samza.apache.org
Cc: Chris Riccomini
Subject: Re: RocksDBException: IO error: directory: Invalid argument
1. I'm running it as another user, but in the user's home directory so it
has no problem writing or reading files.
2. See below.
3. I'm running Windows on my machine so I d
eted before the job was run, it's
failing on the check?
Lukas
-Original Message-
From: Chris Riccomini
Sent: Tuesday, February 17, 2015 1:02 PM
To: dev@samza.apache.org
Cc: Chris Riccomini
Subject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lucas,
I'm w
t;>
>> Lukas
>>
>> -Original Message- From: Chris Riccomini
>> Sent: Tuesday, February 17, 2015 12:12 PM
>> To: Chris Riccomini
>> Cc: dev@samza.apache.org
>>
>> Subject: Re: RocksDBException: IO error: directory: Invalid argument
>>
>
ubject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lukas,
Strange. Having a more detailed look at your logs.
Note: /vagrant is a synced folder, and I think it *does* persist between VM
restarts. But, if you've deleted /vagrant/SamzaJobs/deploy, then the state
should be empty.
Cheers
spin up a new VM. Happens after a
>>> restart as well.
>>>
>>> Lukas
>>>
>>> -Original Message- From: Chris Riccomini
>>> Sent: Tuesday, February 17, 2015 11:01 AM
>>> To: dev@samza.apache.org
>>> Subject: Re: RocksDBExceptio
te:
This happens every time even if I spin up a new VM. Happens after a
restart as well.
Lukas
-Original Message- From: Chris Riccomini
Sent: Tuesday, February 17, 2015 11:01 AM
To: dev@samza.apache.org
Subject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lukas,
Interes
Same thing happens if I delete the whole deploy folder.
Lukas
-Original Message-
From: Chris Riccomini
Sent: Tuesday, February 17, 2015 12:07 PM
To: dev@samza.apache.org
Subject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lukas,
Could you try clearing out the
M, Lukas Steiblys
> wrote:
>
>> This happens every time even if I spin up a new VM. Happens after a
>> restart as well.
>>
>> Lukas
>>
>> -Original Message- From: Chris Riccomini
>> Sent: Tuesday, February 17, 2015 11:01 AM
>> To: d
m: Chris Riccomini
> Sent: Tuesday, February 17, 2015 11:01 AM
> To: dev@samza.apache.org
> Subject: Re: RocksDBException: IO error: directory: Invalid argument
>
> Hey Lukas,
>
> Interesting. Does this happen only after restarting your job? Or does it
> happen the first t
This happens every time even if I spin up a new VM. Happens after a restart
as well.
Lukas
-Original Message-
From: Chris Riccomini
Sent: Tuesday, February 17, 2015 11:01 AM
To: dev@samza.apache.org
Subject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lukas
/vagrant/SamzaJobs/deploy/samza/state/engaged-store
> 36K/vagrant/SamzaJobs/deploy/samza/state
>
> Lukas
>
> -Original Message----- From: Chris Riccomini
> Sent: Monday, February 16, 2015 5:53 PM
> To: dev@samza.apache.org
> Subject: Re: RocksDBException: IO e
ge-
From: Chris Riccomini
Sent: Monday, February 16, 2015 5:53 PM
To: dev@samza.apache.org
Subject: Re: RocksDBException: IO error: directory: Invalid argument
Hey Lukas,
It looks like the exception is actually thrown on get, not put:
at org.apache.samza.storag
Hey Lukas,
It looks like the exception is actually thrown on get, not put:
at org.apache.samza.storage.kv.KeyValueStorageEngine.get(
KeyValueStorageEngine.scala:44)
1. Are you running your job under YARN, or as a local job
(ThreadJobFactory/ProcessJobFactory)?
2. What OS are you runnin
Hello,
I was setting up the key-value storage engine in Samza and ran into an
exception when querying the data.
I added these properties to the config:
stores.engaged-store.factory=org.apache.samza.storage.kv.RocksDbKeyValueStorageEngineFactory
stores.engaged-store.changelog=kafka.eng
25 matches
Mail list logo
