Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:25
    ejsmith synchronize #452
  • 06:25

    ejsmith on elastic7

    Minor (compare)

  • 06:00
    ejsmith synchronize #452
  • 06:00

    ejsmith on elastic7

    Add missing task id (compare)

  • Dec 13 22:43
    ejsmith synchronize #452
  • Dec 13 22:43

    ejsmith on elastic7

    More reindex job changes (compare)

  • Dec 13 15:46
    ejsmith synchronize #452
  • Dec 13 15:46

    ejsmith on elastic7

    Just retry 3 times (compare)

  • Dec 13 15:44
    ejsmith synchronize #452
  • Dec 13 15:44

    ejsmith on elastic7

    More log message changes (compare)

  • Dec 13 14:25
    niemyjski synchronize #452
  • Dec 13 14:25

    niemyjski on elastic7

    Added retry reindex for disconn… (compare)

  • Dec 13 14:09
    niemyjski synchronize #452
  • Dec 13 14:09

    niemyjski on elastic7

    Updated migration to retry sock… (compare)

  • Dec 13 04:51
  • Dec 13 03:28
    ejsmith synchronize #452
  • Dec 13 03:28

    ejsmith on elastic7

    Oops progress (compare)

  • Dec 13 03:04
    ejsmith synchronize #452
  • Dec 13 03:04

    ejsmith on elastic7

    More log formatting (compare)

  • Dec 13 02:02
    ejsmith synchronize #452
Blake Niemyjski
@niemyjski
@woehrl01 we just added the -s flag in the latest nightly hehe
Lukas Wöhrl
@woehrl01
I just executed those, but still no additional exceptions :-/
Blake Niemyjski
@niemyjski
you'll need to configure redis
otherwise the queue event migrations job is just going to queue things to nothing
(in memory queue)
Did the stacks show up in your elastic search instance
Lukas Wöhrl
@woehrl01
no, the stacks are not showing up
I just renabled redis but still no exceptionions
so. I changed job.exe.config to the same values aus web.config (mongodb/redis/elastic) and I reexecuted the statements above for StackMigrationJob, QueueEventMigrationsJob and EventMigrationJob
but, the old exceptions are still not showing up
any further suggestions?
Lukas Wöhrl
@woehrl01
I just enabled, the INFO logging level. and it prints the following: The daterange looks a little bit off?
2015-06-11 17:14:30.9660|INFO|JobRunner|Starting job type "EventMigrationJob" on machine "VM9-DEV"...
2015-06-11 17:14:31.1126|WARN|Bootstrapper|StatsD Metrics is NOT enabled.
2015-06-11 17:14:31.2572|WARN|Bootstrapper|Azure Storage is NOT enabled.
2015-06-11 17:14:32.8286|INFO|MigrationJobBase|Public IP: 79.255.159.7
2015-06-11 17:14:32.8579|INFO|EventMigrationJob|Processing event migration jobs
for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
2015-06-11 17:14:33.4149|INFO|EventMigrationJob|Finished processing event migration jobs for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
Blake Niemyjski
@niemyjski
Yeah that is good it's doing 12 hour day increments
that looks good
anything in the log for migrating stacks
If you want I could jump on a remote meeting for a few minutes and help take a look
Lukas Wöhrl
@woehrl01
yeah, I cleared redis and did all of this again, and with info enabled I get:
2015-06-11 17:21:57.3987|INFO|StackMigrationJob|Migrating stacks 8.000 total 2.711/s...
2015-06-11 17:21:57.4192|INFO|StackMigrationJob|Migrating stacks 8.050 total 2.711/s... etc
looks good so far, except that it's not showing :D
Blake Niemyjski
@niemyjski
we'll what are you using to look at your elastic search content
elastic hq plugin?
Lukas Wöhrl
@woehrl01
I have currently nothing installed to look at the content
just installed elasticsearch for exceptionless
Blake Niemyjski
@niemyjski
go there and then enter in your connection string for elastic
as shown and then connect
it will show you all the indexs / records
Lukas Wöhrl
@woehrl01
looks, good, I have >8000 stacks-v1 about the same count like in mongodb
Blake Niemyjski
@niemyjski
ok
so looks like those were migrated
now just need to migrate events
how many errors do you have?
Lukas Wöhrl
@woehrl01
none, inside of elastic
Blake Niemyjski
@niemyjski
yes but in mongo
Lukas Wöhrl
@woehrl01
about 46k
Blake Niemyjski
@niemyjski
ok
that should be a pretty quick migration
you should just have to queue them
and them run the migration job
Lukas Wöhrl
@woehrl01
it is just queueing from today
Blake Niemyjski
@niemyjski
2015-06-11 17:14:32.8579|INFO|EventMigrationJob|Processing event migration jobs
for date range: 2014-07-31T00:00:00.0000000+00:00-2014-07-31T12:00:00.0000000+00:00
Lukas Wöhrl
@woehrl01
aaaaah, i see , i have to run the last one with -c
Blake Niemyjski
@niemyjski
it looks like it started queueing from 11m ago
ahh yeah
Lukas Wöhrl
@woehrl01
:D
Blake Niemyjski
@niemyjski
sorry :)
my bad
lol