21 | ObjectDB's Database Doctor Incorrect Error Report. Have you set the database page size to 256KB? The maximum supported page size is 64KB ... there will be a clear limit of 64KB. Thank you for this report. To avoid this error use page size of 64KB ... could support the 256KB max page size? For my use case, this would make 4 less disk accesses in the Amazon AWS |
20 | Failed to resize file - file system limitation error with the error below. Can you please advise on next steps? Thank you, Clinton [12161] Page #26356937 has invalid reference from key 'AEA6C33' to child page #7 8764514. [12162] Page #27778657 has invalid reference from key 'A3A28F6CD4E1EF0C1D8DCE59E A9BC9986338B205'|2 to child page #78764515 |
16 | Join performance in ObjectdbSELECT count(e) FROM Meta e, ImageNet i, Page p WHERE e.idImage=i.id AND e.idPage=p.id; So simple ... of an Image and a Page instances instead of direct references. A more JPA conventional variant of your query would be: SELECT count(e) FROM Meta e, ImageNet i, Page p WHERE e.image=i AND e.page=p |
14 | How Should I Configure objectdb.conf to Obtain 256KB Disk IO Requests and Maximize Shared PersistenceManager Entity Cache? caching 1 MB (4 256KB sized pages). The goal is to have frequent PersistenceManager L1 cache hit ... above) appropriate to achieve this goal? CBE CBE Having larger database pages may have other effects (e.g. searching for an object in a larger page could take longer). So, as with most tuning |
14 | Iterating over large result set in memory was quite a challenge even with 3GB heap space. So I did paging using two loops. for (int page=0; page < resultCount; page+=pageSize) { Query q = em.createQuery("query"); for (Tuple t : q.setFirstResult(page).setMaxResults(pageSize).getResultList()) { // work |
4 | Use temporary files to enable very large transactions results), currently the size of a transaction (i.e. the total size of database pages ... your needs. Particularly the unlimited size. The memory problem is with Page instances in memory ... of Page instances. support Support Regarding a new maximum for transaction size. In the long term |
3 | each 1-2 days objects on some objectdb level lock/block each other The two thread dumps show two different waiting situations. The first thread dump shows a page cache lock ... ="*" level="info" /> </general> <database> <size initial="256kb" resize="256kb" page ... application they may refresh the page if the response is too slow (again and again, as |
2 | Querying error - java.lang.ClassCastException: com.objectdb.o.STV small / large objects. ObjectDB splits large objects (> 2000 bytes) into pages. Somehow the stack trace indicates an unexpected state in which the same object is marked as small in one page and as large in another page. Maybe this is the result of switching between the two states when the object |
2 | Database access error , Doctor hanging on trying to repair, production shutdown at our biggest customer ------------------ [1] com.agile.hummingbird.ObjectProperty - Unexpected object count: 49830620 (actual 49830619) Page Content Errors ------------------- [1] Page #16748245 has a non first section entry (at entry 1 ... -------------------------- Group #1: Page#7880349 5:194359909 0/2 0+1954/2699 ... hgzwicker Hans-Georg Zwicker |
2 | [ObjectDB 2.6.9] Unexpected exception (Error 990): 142351618 (actual 142351616) Page Relation Errors -------------------- [1] Page #36099460 unexpected exception: null [2] Page #36099460 last key is null, parent page #43650945 next key is ('3.203.10.00.100000','95798112',2421822 8) [3] Page #36230484 unexpected exception: null [4] Page #36230484 |
